Work on SQLite4 has concluded

Post by X86BSD » Wed, Nov 08, 2017, 1:57 AM UTC

makmanalp wrote: post #56

coleifer wrote: post #44

Earlier quoted context omitted.

I'm jealous you got to hear Dr. Hipp, that sounds cool. Would love to hear more about the circumstances :) Regarding the LSM engine, you can find all the relevant implementation details here: https://sqlite.org/src4/doc/trunk/www/lsm.wiki#summary > The in-memory tree is an append-only red-black tree structure used to stage user data that has not yet flushed into the database file by the system. Under normal circumsta…

I got lucky! It was a class event, and he's known to speak at databases / data systems classes. He's a very fun (and opinionated!) speaker. > The in-memory tree is an append-only red-black tree structure used to stage user data that has not yet flushed into the database file by the system. Hmm, ok, so this contradicts my assumption. Actually, now that I think about it, other LSMs like rocksdb / leveldb work like this…

Post by kijin » Wed, Nov 08, 2017, 2:04 AM UTC

dflock wrote: post #60

oh_sigh wrote: post #30

Earlier quoted context omitted.

What kind of companies sign 35 year support contracts?

I read somewhere the other day that sqlite is used somewhere in Airbus A380 passenger jets, and Airbus have a support contract for it.

Post by ianamartin » Wed, Nov 08, 2017, 2:09 AM UTC

sliverstorm wrote: post #26

Scaevolus wrote: post #3

For context, SQLite4 explored reimplementing SQLite using a key-value store on log-structured merge trees, like RocksDB and Cassandra. I'd be interested to hear why they stopped. Presumably reimplementing SQL on a KV store was seen as not worth it, when applications that are satisfied with an embedded KV store backend (which is much faster and simpler to write!) already have many options.

Everything I hear about SQLite3 always suggests that, essentially, it is considered "done". It does what it is supposed to do with great performance. There is nothing major left to do. If it doesn't meet your needs, pick a different SQL database. Which, while a totally alien concept in the modern software world, is actually a pretty cool thought. (I'm sure under the hood bugs are getting fixed and all)

Post by makmanalp » Wed, Nov 08, 2017, 2:15 AM UTC

interfixus wrote: post #64

coleifer wrote: post #44

Earlier quoted context omitted.

I'm jealous you got to hear Dr. Hipp, that sounds cool. Would love to hear more about the circumstances :) Regarding the LSM engine, you can find all the relevant implementation details here: https://sqlite.org/src4/doc/trunk/www/lsm.wiki#summary > The in-memory tree is an append-only red-black tree structure used to stage user data that has not yet flushed into the database file by the system. Under normal circumsta…

Why does everybody persist in calling the great man Dr. ? He refers to himself as D. Richard Hipp.

Post by jzawodn » Wed, Nov 08, 2017, 2:33 AM UTC

jandrese wrote: post #46

krylon wrote: post #18

Earlier quoted context omitted.

Look at it this way: SQLite3 is (more or less) slowly becoming SQLite4, except for the parts that did not work out. It is not as shiny, but in the long run, you still get all the goodness. Nevermind the name / version number.

It's basically the Perl 5 of the DB world.