this post was submitted on 08 Nov 2025

149 points (97.5% liked)

Programmer Humor

27428 readers

1936 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 2 years ago

MODERATORS

anzo@programming.dev

Feyter@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

149

SQLite (programming.dev)

submitted 1 week ago by tatterdemalion@programming.dev to c/programmer_humor@programming.dev

19 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] ulterno@programming.dev 0 points 1 week ago (1 children)

SQLite puts all of the responsibility on users to handle this

Thanks for the explanation.
I feel like the one who decided this behaviour, expected the users of the database, to make their own system of prioritising the transactions.

[–] F04118F@feddit.nl 2 points 1 week ago

More likely: SQLite is built to be small, simple and lightweight, not to be super highly concurrent.

If this situation happens rarely, just make sure you have a retry on the query. If it happens often, switch to postgres.