One SQL to Rule Them All · HackerPapers discussions

One SQL to Rule Them All — mentioned by cube2222

Mon, 07 Jun 2021 15:58:22 GMT

Looking at the comments I see there are more and more such projects, that's great! Declarative interfaces rule! Anyways, I too felt a void to be filled with tools like these, so I (and a couple of other folks) developed OctoSQL[0], check it out if you like this. It lets you query json, csv, and various databases using SQL, and also let's you join between them. It differs from most of the other tools in that it also supports streaming data sources using temporal SQL extensions. (Inspired by the great paper, One SQL To Rule Them All[1]) [0]: https://github.com/cube2222/octosql [1]…

Paper and discussion history. A mention is not an endorsement.

One SQL to Rule Them All — mentioned by BenoitP

Sun, 18 Apr 2021 19:58:28 GMT

> this would still leave the problem where each transactions causes two deletes and two inserts Indeed! You might be interested in the '6.5 Materialization Controls' section of this paper: https://arxiv.org/pdf/1905.12133.pdf They intend to add these extensions: SELECT ... EMIT STREAM AFTER DELAY INTERVAL '6' MINUTES ; -- to fix the output multiplication you mention SELECT ... EMIT STREAM AFTER WATERMARK ; -- this should fix the two deletes and two inserts I don't know if this is still in active development, though. There has been no news since the paper got published 2 years ago. > It…

Paper and discussion history. A mention is not an endorsement.

One SQL to Rule Them All — mentioned by james_woods

Fri, 22 Jan 2021 08:39:00 GMT

Where and how in dataflow is late data being handled? How can I configure in which ways refinements relate? These questions are the standard "What Where When How" I want to answer and put into code when dealing with streaming data. I was not able to find this in the documentation, but I only spent a few minutes scanning it. https://www.oreilly.com/radar/the-world-beyond-batch-streami... https://www.oreilly.com/radar/the-world-beyond-batch-streami... Also "Materialize" seems not to support needed features like tumbling windows (yet) when dealing with streaming data in SQL…

Paper and discussion history. A mention is not an endorsement.

One SQL to Rule Them All — mentioned by chrisjc

Wed, 12 Aug 2020 16:04:13 GMT

Are you referring to this? https://arxiv.org/abs/1905.12133 HN Link: https://news.ycombinator.com/item?id=20059006

Paper and discussion history. A mention is not an endorsement.

One SQL to Rule Them All — mentioned by cangencer

Wed, 12 Aug 2020 13:01:12 GMT

It's not very different than normal SQL. Imagine that instead of a finite result set, you instead have a never ending result set. You can also roughly map operations like windowed aggregation into SQL with some additional syntax. This paper gives a pretty good overview, even though we don't fully agree with the model presented here: https://arxiv.org/abs/1905.12133

Paper and discussion history. A mention is not an endorsement.

One SQL to Rule Them All — mentioned by yarapavan

Wed, 03 Jul 2019 15:51:33 GMT

Link to SIGMOD'19 paper - https://arxiv.org/abs/1905.12133

Paper and discussion history. A mention is not an endorsement.

One SQL to Rule Them All — HN submission

Fri, 31 May 2019 07:56:03 GMT

One SQL to Rule Them All: Management of Streams and Tables

260 points; 35 discussion replies on HN. Paper and source history. A submission is not an endorsement.