News for hackers. Stuff that matters.
Re:Poor man's bitemporal data system in SQLite and Clojure by necubi on Wednesday September 03, 2025 @06:04PM (#45120880)
It's not particularly rare in analytical databases/query engines, nearly all of which support AsOf joins these days, including

  * Clickhouse
  * DuckDB
  * BigQuery
  * Snowflake
  * QuestDB
Re:Poor man's bitemporal data system in SQLite and Clojure by refset on Wednesday September 03, 2025 @08:22PM (#45121943)
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 also reducing the need for many user-defined timestamp columns.

In a bitemporal database, every regular looking join over the current state of the world is secretly an AsOf join (across two dimensions of time), without constantly having to think about it when writing queries or extending the schema.

Re:Poor man's bitemporal data system in SQLite and Clojure by sterlinm on Wednesday September 03, 2025 @11:40PM (#45123286)
This is the book I like for an overview of the problem. https://www.amazon.com/Temporal-Relational-Kaufmann-Manageme...