Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> sqlite3

I know sqlite3 is great, but I've always found it much more annoying to use it on a server for small side projects than just using Postgres where I could just connect to the prod instance from my local machine and run some queries to look at the data. With sqlite I'd always have to sync files, set up volumes, make sure permissions are correct vs. just setting an environment variable to a PG instance.



From what I understand, the sqlite3 comment was made it context of the Solid libraries. Basically common Redis-backed functionality can now be sqlite3-backed instead.

I do share your preference on using Postgres as the main database. Having that as the main db with sqlite3 used for auxiliary functionality sounds great.


It's not much different than with Postgres:

    ssh your-server sqlite3 /tmp/path/to/your/db.sqlite3
Or if you're using Kamal, then the choice of database is completely transparent:

    kamal app exec -i --reuse bin/rails console




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: