News for hackers. Stuff that matters.
Re:Why SQLite succeeded as a database (2016) by mrighele on Thursday February 20, 2020 @01:23AM (#22373107)
> The trick is to use a single connection and let SQLite handle the serialization for you, rather than try to manage multiple connections to the same file in code (i.e. one connection per logical operation sucks for SQLite).

It seems to me that in that case you cannot use transactions though, or am I wrong ?

Re:Why SQLite succeeded as a database (2016) by easytiger on Thursday February 20, 2020 @03:25AM (#22373580)
You can use transactions. They determine batch persistence of the data rather than persisting every insert.

You can just batch them up by

    mod N inserts or Z milliseconds
if you have enough data If you don't particularly care you can disable syncing too.