The next-gen SQLite won't look like SQLite

Re:The next-gen SQLite won't look like SQLite by DougN7 on Sunday January 18, 2026 @10:05AM (#46668351)

I wouldn’t call this next-gen SQLite. How can it be when the “QL” of SQLite is “Query Language” and this doesn’t have one? This is an object serialization library.

[ Parent | on HN ]

Re:The next-gen SQLite won't look like SQLite by beardyw on Sunday January 18, 2026 @11:30AM (#46669159)

Exactly. SQLite is in use in millions[1] of places, all using SQL. If you want something else don't try to steal the name.

[1] this figure is based on no research

[ Parent | on HN ]

Re:The next-gen SQLite won't look like SQLite by delegate on Sunday January 18, 2026 @10:19AM (#46668484)

Not really. This db allows traversing the (deeply nested) data structures without loading them into memory. Eg. In Clojure you can do ``` (get-in db [:people "john" :address :city]) ```

Where `:people` is a key in a huge (larger than memory) map. This database will only touch the referenced nodes when traversing, without loading the whole thing into memory.

So the 'query language' is actually your programming language. To the programmer this database looks like an in-memory data structure, when in fact it's efficiently reading data from the disk. Plus immutability of course (meaning you can go back in history).

[ Parent | on HN ]