qaz@lemmy.world to Programmer Humor@programming.devEnglish · 2 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 · 2 months agomessage-square58fedilink
minus-squareFargeol@lemmy.worldlinkfedilinkarrow-up71·2 months ago“You know what ELSE everybody likes? Postgres! Have you ever met a person, you say, ‘Let’s use some Postgres,’ they say, ‘Hell no, I don’t like Postgres’? Postgres is perfect!”
minus-squareThe Bard in Green@lemmy.starlightkel.xyzlinkfedilinkarrow-up33·2 months agoYeah! Postgres is great! Mutters something under his breath about MariaDB.
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up15·2 months ago MariaDB Let’s schedule a meet-up at 00/00 year 0000 to talk about it.
minus-squaresomerandomperson@lemmy.dbzer0.comlinkfedilinkarrow-up11·edit-22 months ago elephant walks in
minus-squareRustyNova@lemmy.worldlinkfedilinkarrow-up14·2 months agoI 100% agree… If you don’t need portable databases. For those, everybody like SQLite (even if it can be annoying sometimes)
minus-squarewetbeardhairs@lemmy.dbzer0.comlinkfedilinkarrow-up4·2 months agoYou can pry sqlite out of my cold dead hands. Because I’ll probably die while using it out of frustration due to the poor performance of triggers.
minus-squareRustyNova@lemmy.worldlinkfedilinkarrow-up3·2 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-22 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.
“You know what ELSE everybody likes? Postgres! Have you ever met a person, you say, ‘Let’s use some Postgres,’ they say, ‘Hell no, I don’t like Postgres’? Postgres is perfect!”
Yeah! Postgres is great!
Let’s schedule a meet-up at 00/00 year 0000 to talk about it.
I 100% agree… If you don’t need portable databases. For those, everybody like SQLite (even if it can be annoying sometimes)
You can pry sqlite out of my cold dead hands. Because I’ll probably die while using it out of frustration due to the poor performance of triggers.
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.