300
: ( (lemmy.dbzer0.com)
submitted 2 months ago by to c/programmer_humor@programming.dev
34 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 49 points 2 months ago (2 children)

I think you got the wrong caption. It's the world if SQLite supported multiple concurent writes.

Stupid transaction deadlocks...

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 10 points 2 months ago (3 children)

    In my case, I want to use sqlite locally, for development, but I don't want to add a load of jank to handle booleans for sqlite.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 14 points 2 months ago (2 children)

    I use rust's SQLx which map bools to numbers so it must be a problem with your connector maybe

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 7 points 2 months ago (1 child)

    That’s what I like about Ruby ORMs. They did all the conversion for you, and you could have SQLite on your dev box, Postgres on the test server and MySQL on the annoying production host that wouldn’t run anything else.

    This was 18 years ago though.

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

    WAL mode makes writes a lot faster, which is sufficient for a bunch of use cases. Writers do still need to wait, but they have to wait for a shorter duration. It's still not the right choice for write-heavy use cases, of course.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •