refset

7 ms·

31.
by refset 1y ago
The world deserves something better than json_agg. For XTDB we coined NEST_ONE and NEST_MANY: https://xtdb.com/blog/the-missing-sql-subqueries The output format is either raw Arrow DenseUnions (e.g. via FlightSQL) or T
32.
by refset 1y ago
AsOf join in those systems solves a rather narrow problem of performance and SQL expressiveness for data with overlapping user-defined timestamps. The bitemporal model solves much broader issues of versioning and consistent reporting whilst
33.
by refset 1y ago
That only covers the 'transaction time' axis though? And the page says retention is limited to 1 week. No doubt useful for some things, but probably not end-user reporting requirements.
34.
by refset 1y ago
> waiting for that eagerly! Wait no longer! I just updated the page with the unlisted video link: https://youtu.be/6Q_pAI20QPA We are hoping to record another (more polished) session with Professor Snodgrass soon :)
35.
by refset 1y ago
tl;dr CREATE VIEW IF NOT EXISTS world_facts_as_of_now AS SELECT rowid, txn_time, valid_time, e, a, v, ns_user_ref, fact_meta FROM ( SELECT *, ROW_NUMBER() OVER ( PARTITION BY e, a ORDER BY valid_pre
36.
by refset 1y ago
An ability to add a custom thumbnail image to a deep link might be a good compromise.
37.
by refset 1y ago
Julian Hyde (Apache Calcite, Google) gave a crisp presentation on this and how SQL could express 'measures' to bridge the gap: https://communityovercode.org/wp-content/uploads/2023/10/mon... &g
38.
by refset 1y ago
> Hollow employs compression techniques Given how prominently 'compression' gets mentioned I was excited to learn more, but it looks like it simply amounts to using GZIPInputStream/GZIPOutputStream within the blob APIs, or
39.
by refset 1y ago
The dissertation covers extensive details, but on your last point at least it describes: > 2.2.1 Evaluation by Default. One of the major syntactic differences between Dyna and other logic programming languages is that Dyna evaluates an e
40.
by refset 1y ago
> Dyna3 — A new implementation of the Dyna programming language written in Clojure There are some epic looking Clojure namespaces here, e.g. this JIT compiler https://github.com/argolab/dyna3/blob/master&#x
41.
by refset 1y ago
> In the end, one way of stating the conclusion of this model is that a social group is a form of tool for economic benefit, and the other tools we create build on the cognitive underpinnings of social interactions. Indeed, in the modern
42.
A Quantitative Model of Trust as a Predictor of Social Group Sizes(arxiv.org)
1 points by refset 1y ago|1 comments
43.
by refset 1y ago
Datomic offers the ability to declare a "composite index" which can help to accelerate some kinds of access patterns but can't solve 6NF join overheads entirely. If you want guaranteed read performance then denormalized views
44.
by refset 1y ago
Ah, apologies if I jumped the gun - but seeing the page was live and with all the great talks lined up already ...I couldn't resist sharing!
45.
Future Data Systems Seminar Series – Fall 2025 (draft schedule)(db.cs.cmu.edu)
2 points by refset 1y ago|2 comments
46.
by refset 1y ago
The UK at least https://en.m.wikipedia.org/wiki/Poisoning_of_Sergei_and_Yuli...
47.
by refset 1y ago
The thing that tipped me over the edge into learning ClojureScript was the news almost exactly a decade ago about achieving self-hosted compilation with eval [0] (kudos David!). In the end that specific capability was not quite practical en
48.
by refset 1y ago
Lotus Notes always deserves a mention in these threads too, as 1989's answer to local-first development. CouchDB was heavily inspired by Notes.
49.
by refset 1y ago
These things should become plausible once the engine supports recursive CTEs and incremental view maintenance. In the meantime you could exploit Arrow interop with other engines (while keeping XTDB as the source of truth) - people have been
50.
by refset 1y ago
I agree the opportunity is still there, although the long game keeps getting longer. Prof. Viktor Leis suggested [0] that SQL itself - being so complex to implement and so ineffectively standardized - may be the biggest inhibitor to faster
51.
by refset 1y ago
The HTAP vision was essentially built on the traditional notion that a database is a single 'place' where both transactions happen and complex queries run. Rich Hickey argued [0] that place-orientation is bad and that a database s
52.
Diskless Kafka is the Tide, and it's Rising(aiven.io)
3 points by refset 1y ago|0 comments
53.
by refset 1y ago
It's not clear to me that the _entire_ Neon stack is OSS and available to self-host (though they do share a lot of OSS code, which is great), and in any case, it's not currently supported/documented beyond some "local de
54.
by refset 1y ago
> you use S3 as bottomless storage for Postgres [...] Why are people paying? It's vastly more complicated to do this efficiently than you might imagine. Postgres' internal architecture is built around a very different set of
55.
Update Reconsidered, delivered?(xtdb.com)
2 points by refset 1y ago|0 comments
56.
by refset 1y ago
> Maybe there are better patterns out there to make this cleaner SQL:2011 temporal tables are worth a look.
57.
by refset 2y ago
David Harel, the creator of statecharts, also developed the Behavioral Programming [0] 'b-thread' model motivated by a similar vision for append-only programming - it has been discussed on HN previously e.g. https://new
58.
by refset 2y ago
In XTDB you can now use (trailing-friendly) commas in this scenario too, instead of ANDs: https://github.com/xtdb/xtdb/pull/3985
59.
The Decline and Fall of In-Memory Database Systems (2024)(cedardb.com)
2 points by refset 2y ago|0 comments
60.
by refset 2y ago
> It's relatively easy to implement your own temporal tables on most existing databases It gets tricky when you need to change the schema without breaking historical data or queries. SQL databases could do a lot more to make immutab

More ›