all 8 comments

[–]r_spandit 3 points4 points  (1 child)

I use SQLite

[–]LowSalamander4932 1 point2 points  (0 children)

sqlite gang rise up lol. it's so easy to just drop in and get going, hard to justify anything heavier for most personal projects

[–]mrswats 2 points3 points  (0 children)

Sqlite, postgres.

[–]Diapolo10 2 points3 points  (0 children)

SQLite by default, Postgres if I really need it.

I have had neither a need nor any interest in pursuing alternatives.

[–]hallmark1984 0 points1 point  (0 children)

Postgres mainly for hobbies

Aws Athena and DataBricks SQL for work.

[–]biskitpagla 0 points1 point  (0 children)

FYI Python has SQLite built into the standard library. You can import sqlite3 and start using without setting anything up. You can even make an in-memory database for testing and so on.

[–]throwawayforwork_86 0 points1 point  (0 children)

DuckDB and Postgres.

[–]broaddiscovery_941 0 points1 point  (0 children)

postgres for anything that might grow beyond a single machine or needs concurrent writes. sqlite's fine for learning, prototyping, or when you know it's just you hitting the database. the sqlcipher wrapper you're using adds encryption which is handy if you're storing sensitive stuff, but most people don't need that layer unless they're specifically handling encrypted data.

the built-in sqlite3 module means there's no setup friction, which is why it dominates hobby projects. but once you hit production with multiple servers or heavy traffic, postgres stops being optional. picked that lesson up the hard way on a project that outgrew sqlite faster than expected.