News for hackers. Stuff that matters.

A comment on SQLite is not a toy database. Parent comment

Re:SQLite is not a toy database by Thaxll on Thursday March 25, 2021 @01:59PM (#26583358)
"The trick for extracting performance from SQLite is to use a single connection object for all operations, and to serialize transactions using your application's logic rather than depending on the database to do this for you."

It's not the right approach because it's hard to get right, you want to offload that to the DB.

[ Parent | on HN ]
Re:SQLite is not a toy database by bob1029 on Thursday March 25, 2021 @02:04PM (#26583418)
It's actually not that hard to get right. You can put a simple lock statement around a SQLiteConnection instance to achieve the same effect with 100% reliability, but with dramatically lower latency than what hosted SQL offerings can provide.

Also, the only reason we ever want to lock a SQLiteConnection is to obtain a consistent LastInsertRowId. With the latest changes to SQLite, we don't even have to do this anymore as we can return the value as part of a single invocation.

[ Parent | on HN ]
Re:SQLite is not a toy database by warmwaffles on Thursday March 25, 2021 @11:59PM (#26588612)
You won't have to worry about the last insert row id anymore. `RETURNING` was added recently. Enjoy the speeeed.
[ Parent | on HN ]
Re:SQLite is not a toy database by edwinyzh on Friday March 26, 2021 @03:11AM (#26589537)
Yes, this is exactly how mORMot (https://github.com/synopse/mORMot) implements the DB server with SQLite.
[ Parent | on HN ]