Suggestion: SQLite backend

[sammcj]

Looking at this neat little project I was a bit surprised that it needed a full (OR)DBMS.

I love PostgreSQL, but sometimes for small, self-contained projects I think that SQLite is (perhaps) a wise choice - especially when it's going to often be run in Docker containers for local use as it saves having to pull down a full PostgreSQL Docker image and run a container for it.

If it's not worth the effort feel free to reject the suggestion :)

[davidfetter]

With utmost respect, this isn't the era when a few megabytes' worth of infrastructure is even noticeable. Is it really all that burdensome to be running PostgreSQL?

[sammcj]

I understand what you’re saying, but I don’t think that to run a simple app you should have to install, configure and maintain a full database server.

It’s not about the cost of running it - it’s about the practicality. For example if you want to run this ad-how on your laptop when you need it - it’s a pain to have to install and run a database server.

[owenthereal]

Using SQLite locally could be a convenient option, as it reduces dependencies and simplifies running jqplay on your machine without relying on the hosted version.

[davidfetter]

Using SQLite locally could be a convenient option, as it reduces dependencies and simplifies running jqplay on your machine without relying on the hosted version.

It's coming up on five years since the idea was suggested, thus far without so much as a hint of a patch. I'm thinking this may not be as easy to do as it might have first appeared.

[owenthereal]

This was challenging to achieve before, but it should now be much easier with the latest rewrite using Prisma. You can refer to the Prisma data source documentation for more details.