qaz@lemmy.world to Programmer Humor@programming.devEnglish · 5 months agoWho needs MongoDB when you have JSONB?lemmy.worldexternal-linkmessage-square58fedilinkarrow-up1320arrow-down13
arrow-up1317arrow-down1external-linkWho needs MongoDB when you have JSONB?lemmy.worldqaz@lemmy.world to Programmer Humor@programming.devEnglish · 5 months agomessage-square58fedilink
minus-squareRustyNova@lemmy.worldlinkfedilinkarrow-up3·5 months agoTbh trigger performance isn’t that much of a concern unless you need to write lots of data, which most usage don’t need. Also try check statements instead or even re-evaluate your schema to prevent them if you really need to. Personally my death would be multiple write transaction deadlocks. Sadly it doesn’t play that well with async code, like with sqlx (rust).
minus-squaretatterdemalion@programming.devlinkfedilinkarrow-up2·edit-25 months agoMy death was the fact that table lock acquisition is not FIFO. https://sqlite.org/forum/forumpost/8d7d253df1b9811b4b76c2c4c26ac0740e73d06e9edfeb2ab8aabaebd899cbc8 Thankfully I can at least have FIFO in a single process by wrapping every write transaction in a mutex. P.S. can’t wait for turso’s SQLite replacement to have feature-parity and sqlx support.
Tbh trigger performance isn’t that much of a concern unless you need to write lots of data, which most usage don’t need.
Also try check statements instead or even re-evaluate your schema to prevent them if you really need to.
Personally my death would be multiple write transaction deadlocks. Sadly it doesn’t play that well with async code, like with sqlx (rust).
My death was the fact that table lock acquisition is not FIFO.
https://sqlite.org/forum/forumpost/8d7d253df1b9811b4b76c2c4c26ac0740e73d06e9edfeb2ab8aabaebd899cbc8
Thankfully I can at least have FIFO in a single process by wrapping every write transaction in a mutex.
P.S. can’t wait for turso’s SQLite replacement to have feature-parity and sqlx support.