sqlite_modern_cpp VS sqlite_orm

I just wrote something using https://github.com/SqliteModernCpp/sqlite_modern_cpp, which I chose after 10 minutes of searching around. Should I have used yours instead? How should I decide?

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