327
Who needs MongoDB when you have JSONB? (lemmy.world)
submitted 1 year ago by to c/programmer_humor@programming.dev
60 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 15 points 1 year ago (4 children)

I 100% agree... If you don't need portable databases. For those, everybody like SQLite (even if it can be annoying sometimes)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 1 year ago (3 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 1 year ago (2 children)

    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).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago* (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 1 year ago

    This is also part of my death, because it's much easier to not deadlock when you are FIFO.

    Personally I went for the nuclear option, and any transaction is sent as a tokio task to make sure the transaction keeps getting polled despite other futures getting polled. Coupled with a generous busy timeout timer (60secs) and Wal mode, it works pretty well.

    Probably should also put the mutex strategy (perhaps a tokio semaphore instead?) although due to lifetimes it might be hard to make a begin() function on my DB pool wrapper.

    ... Congratulations. You nerd snipped me. Time for it to go on the todo stack.

    Hyped for it too, but wouldn't use until sqlx suport. Compile time checked queries are just so good. I don't use rustsqlite for that reason alone (you often don't need async SQLite anyways)

  • permalink
  • fedilink
  • source
  • parent