Maybe I'm missing something obvious but all I see is the source amalgamation, not the files used to generate the giant source code file. Did they take the SQLite source amalgamation and write their changes directly against that?

For context, this is The Amalgamation: https://www.sqlite.org/amalgamation.html

> The content of [LiteTree] can be verified via making a diff with the sqlite amalgamation version 3.27.2

Did they actually write it on top of the SQLite amalgamation instead of a separate tree? That thing is 228140 lines long!

That doesn't seem like a very sustainable way to maintain compatibility with newer released versions of sqlite.

Oh I'm sure the genius behind the block chain tech knows what they're doing

see also https://github.com/dolthub/dolt

Creator of Dolt here. Thanks for the mention! My cofounder is writing a blog on Monday about how to run Dolt embedded like SQLite.

Glad to see more people exploring the space.

I just wanted to say thanks for https://github.com/dolthub/go-mysql-server

This is incredibly useful for anyone who wants to build their own DB or wrap another datasource so it's queryable via MySQL protocol.

Oh, crikey, that's handy for a lot of things which will only allow you the choice of MySQL or Postgres.

Posted this in our Discord :-)

Came here to post this. I'm super interested in versioned databases. They provide so many things "you're going to want" (audit log of changes over time, point in time queries, undo/redo) "for free". Dolt is the one I'm most hopeful for.

ooh this is really cool. hopefully it works with something like spatialite. i have a need to store the OpenStreetMap road network at various points in its history and being able to branch and update those branches without each consuming gigabytes more of data would be super useful.

This reminds me of branching in PlanetScale (https://docs.planetscale.com/concepts/branching). I am not an expert, though. Is this a similar approach in terms of use case?

The branching in PlanetScale is for schemas (your team branch out to develop your database, and merge the branch when new development has completed)