• ulterno@programming.devEnglish
    0·
    1 month ago

    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·
      29 days 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.