It's cool that this is possible, is this just for fun or are there good use-cases for this?

samwillis 9 hours ago | parent | next [-]

It's now used by a huge number of developers for running local dev environments, and emulating server products (Google firebase and Prisma both embed it in their CLI). Unit testing postgres backed apps is also made significantly easer with it.

▲

t_mahmood 8 hours ago | parent | prev | next [-]

One use case, when doing unit tests, Docker containers, would make it too expensive with many tests. SQLite's type checking is far less strict than Postgres, which would not catch errors that would occur the real database due to type mismatch.

Having something like this, that I can quickly spawn and know, I am getting exact behavior as prod database would be a lifesaver!

▲

npodbielski 9 hours ago | parent | prev | next [-]

Hmm single user website run as HTML from some folder? I guess you could embed this from s3 for multiple users but probably this would be like running multiple engines from the same dir.

▲

ekjhgkejhgk 9 hours ago | parent [-]

> Hmm single user website run as HTML from some folder?

Why not just sqlite then?

	▲	somat 9 hours ago \| parent \| next [-]
		Postgres features are much nicer, honestly if you are using any sort of orm none of this matters. by design they isolate you from many of the more interesting features of the database. And in general this is probably a good thing. But if you enjoy hand writing artisanal sql postgres is far more pleasant to use than sqlite, not that sqlite is bad, it is very good, just... thin after using pg.
	▲	vincnetas 9 hours ago \| parent \| prev [-]
		More SQL functionality?

▲

rozenmd 8 hours ago | parent | prev [-]

I use it for realistic(ish) testing of my hono API, big fan