News for hackers. Stuff that matters.

A comment on SQLite is not a toy database. Parent comment

Re:SQLite is not a toy database by OldHand2018 on Thursday March 25, 2021 @11:33AM (#26581515)
Well, let me throw out a crazy idea:

Nobody said you have to use a single database/file. Obviously, you are going to want to spend a couple minutes thinking about referential integrity. But how often do you delete records in your web app?

[ Parent | on HN ]
Re:SQLite is not a toy database by quesera on Thursday March 25, 2021 @11:48AM (#26581725)
UPDATE is also a write, and references crossing files sounds like a nightmare.

If your deployment environment has serious constraints, I'm sure you could make it work. The product you deliver would be SQLite + custom DBI layer to hide SQLite's limitations.

It would be a lot more work, and not be as robust or scalable, compared to a more traditional selection. But I can imagine cases where it would be appropriate.

[ Parent | on HN ]
Re:SQLite is not a toy database by HelloNurse on Thursday March 25, 2021 @12:24PM (#26582194)
A big database id not an issue. Contention requires a large number of writers, not a large amount of cold data.
[ Parent | on HN ]
Re:SQLite is not a toy database by kuschku on Thursday March 25, 2021 @12:44PM (#26582458)
As an IRC client with an SQLite backend: several hundred times per second.

Per user.

While reads are more like once every day per user.

[ Parent | on HN ]