SQLite VS sqlite_orm

If you are into alternative storage engines for SQLite, there is also an LSM (Log-Structured Merge-tree) extension in the main repository that is not announced nor documented but seems to work. It’s based on the SQLite 4 project.

https://github.com/sqlite/sqlite/tree/master/ext/lsm1

https://www.charlesleifer.com/blog/lsm-key-value-storage-in-...

The sqlite code base is really well done. Lots of documentation.

https://github.com/sqlite/sqlite

Especially the VM part: https://github.com/spandanb/learndb-py/blob/master/learndb/v...

Compare it with this: https://github.com/sqlite/sqlite/blob/master/src/vdbe.c

That's said, I'm curious how complete this LearnDB is. SQLite is hard to read not only it's old but also it covers a lot of SQL and following SQL spec makes hings complicated. SQLite has great test suite so it's nice if you run the suit against this implementation.

Correct, see the github mirror[1]. I don't know how well supported that feature is compared to main branch. If it was completely stable, then it would have already landed in the main stable branch. Clarity about the roadmap of that branch would be nice.

1. https://github.com/sqlite/sqlite/tree/begin-concurrent

Including comprehensive comments, documentation and tests in a codebase takes time and effort.

Failing to do so creates code that is very difficult to maintain or for someone new to the codebase to understand.

However, time and effort may not be what the organization wants to pay for, and individuals may view their own incomprehensible code as something like job security, as they can't be replaced by someone else easily.

As an example of complicated code that's still well-documented, the open-source sqlite code is a good example, about 1/4 of the B-tree file is comments, every time a variable is defined there's a short note explaining what it's used for, every function has a comment header that's comprehensive, such that someone new to the codebase could construct a map of how it all works fairly quickly. It's a good model for how to avoid the problem:

https://github.com/sqlite/sqlite/blob/master/src/btree.c

Obligatory "how does it compare to" https://github.com/fnc12/sqlite_orm ?

I had some success with sqlite_orm, but more generally I'd just recommend to pick a lib that fit your needs and read its examples/docs.

For SQLite, I like sqlite_orm

This one thing I feel like C++ has lacked in: a good, generic, SQL ORM. There is sqlite_orm which is really nice, but only for SQLite. Anyone have any other suggestions?

Probably the most popular ORM for modern C++ is https://github.com/fnc12/sqlite_orm. I've never used it personally. But if you configure SQLite to disable all the barriers and all synchronisation, I think you'll find it goes very, very quickly even with the ORM layer in between.

Hey folks. I've posted my new `SQLiteORM` lib today here on GitHub https://github.com/fnc12/sqlite-orm-swift . It is the same lib I've written with C++ before https://github.com/fnc12/sqlite_orm . It uses keypath instead of `Codable` protocol to serialize and deserialize objects. If you need to use SQLite database inside your Swift project and you hate writing SQL queries using raw strings then you may like this lib.

I was leaning towards SQLite (along with sqlite_orm ) since I thought my data might be more relational and I used to work with databases a lot more. And I can use a SQLite browser app to view my data. But I'm wondering if doing serialization with a library like cerial or Boost's would be better.

For the brief time I've used sqlite_orm, I've really liked it: https://github.com/fnc12/sqlite_orm