refset

11 ms·

211.
by refset 3y ago
> I don’t understand how there hasn’t been more innovation in this space I think it's simply that most businesses and investors don't register SQL as having any real problems, and especially now with a resurgent interest in SQL
212.
by refset 3y ago
> Lest you think is just one weird corner of the sql spec, I found this helpful diagram explaining how the scoping rules work (from Neumann and Leis, 2023) It's an excellent diagram, it really conveys the dissonance. Incidentally I
213.
SQLPage – Building a full web application with nothing but SQL queries [video](youtube.com)
41 points by refset 3y ago|12 comments
214.
by refset 3y ago
> Btw, if you have a reference to the creation of Datalog older than the one I linked to, please share it 1982 was as far as I got last time I went digging: https://news.ycombinator.com/item?id=34819400
215.
by refset 3y ago
> don't have to have two separate worlds for queries and other logic That's definitely the dream. Another point along that spectrum (from the author of Apache Calcite): https://github.com/hydromatic/morel
216.
by refset 3y ago
But only if the data is valuable enough to cover the (much) higher costs that come with those assumptions.
217.
by refset 3y ago
There's more potential applicability/overlap for columnar relational engines (vs. row stores) - this 2023 paper offers some useful background: https://arxiv.org/pdf/2308.08702.pdf
218.
by refset 3y ago
To add to this description, the Prolog-derived syntactic core of Datalog (the Horn clauses and facts) can be viewed as a combination of "unification" and mutually recursive rules to find a fixpoint over your data+query. It's
219.
by refset 3y ago
I fully agree with what Prime says at the end - Joran has really set a new bar here for all future database presentations. Hearing that the entire TigerBeetle domain logic lives in a single file [0] (and is intended to be pluggable for othe
220.
by refset 3y ago
The previous interview on this Clojure-in-Banking theme (featuring Griffin [0]) attracted quite a lot of discussion here before: https://news.ycombinator.com/item?id=37313183 [0] https://griffin.com
221.
Clojure in Banking: Treasury Prime(juxt.pro)
2 points by refset 3y ago|1 comments
222.
by refset 3y ago
Agreed - the main reason I switched to KDE from Gnome was so I could have a vertical taskbar.
223.
by refset 3y ago
> I much prefer when you start with a big-blob of joins to define the data source before getting into the applied operations That's essentially the model we've chosen for XTQL, with the addition of a logic var unification scope
224.
Prototype Compiler from SaneQL to SQL(github.com)
1 points by refset 3y ago|0 comments
225.
by refset 3y ago
One such effort: https://github.com/omnigres/omnigres
226.
by refset 3y ago
"Programming with hand tools" (Tim Ewald, Clojure Conj 2013) is a very memorable talk on this theme: https://youtu.be/ShEez0JkOFw
227.
by refset 3y ago
According to Wikipedia: > The original name SEQUEL, which is widely regarded as a pun on QUEL, the query language of Ingres, was later changed to SQL (dropping the vowels) because "SEQUEL" was a trademark of the UK-based Hawker
228.
by refset 3y ago
Thanks, yes protocol-aware recovery was the context. Pretty sure I first heard it described in Joran's QCon London 2023 talk here: https://youtu.be/_jfOk4L7CiY?t=1460 > If you want your distributed database to maxim
229.
by refset 3y ago
I would guess so, yes.
230.
by refset 3y ago
Consensus protocols, durability and transactional semantics are (should be) closely coupled. I recall TigerBeetle discussing somewhere how they could achieve better throughput and durability guarantees by combining replication/recovery
231.
by refset 3y ago
I have never researched the timeline properly to understand at which point the concept/code got ditched, but it was part of Stonebraker's 1985 vision: https://dsf.berkeley.edu/papers/ERL-M85-95.pdf > POSTQ
232.
by refset 3y ago
The issue is the complexity of figuring out appropriate JSON-compatible serializations and getting the implementation correct for every single column in use. A simple example would be round-tripping the Postgres money type using salary::num
233.
by refset 3y ago
It's definitely a reasonable trade-off given the circumstances. Do you know whether Supabase teams who use this extension simply avoid using any non-JSON Postgres types? Or do they lean on workarounds (e.g. JSON-LD encoding)?
234.
by refset 3y ago
It's especially tragic knowing that Postgres did originally have system-time-like versioning built-in. Instead we get to enjoy being upsold on proprietary ETL-to-Redshift, AlloyDB, etc.
235.
by refset 3y ago
Limited to JSONB types though, by the looks of it.
236.
by refset 3y ago
> which is probably why it's promoted so much I think what you're actually observing is simply that Postgres is by far the most vendor-neutral DBMS (/API) available, and therefore the volume of conversation & marketing
237.
by refset 3y ago
Better still, take a look at Nile's "tenant virtualization" concept: https://www.thenile.dev/
238.
by refset 3y ago
> the Query Graph Model (QGM) representation is quite abstract and hardcodes many properties, making it exceptionally difficult to understand. Its claimed extensibility is also questionable. I don't know much about the context, but
239.
MPAs vs. SPAs: The False Dichotomy(thomascothran.tech)
2 points by refset 3y ago|0 comments
240.
by refset 3y ago
On page 4 of "A Critique of Modern SQL And A Proposal Towards A Simple and Expressive Query Language" [0] (recently published at CIDR 2024) there's a great diagram covering this and many other "semantical ordering"

More ›