Back

@amapanda I fully agree on that, but that is an artifact of SQLite itself not supporting multithreading. My solution for that is having one thread being the one that interacts with the database and then using channels to get the data where it needs to be.

I haven’t implemented it for writing yet, but for reading (SQLite to web service) it works quite well.

Of course you then have the channel overhead to deal with … either that or mutex locking …

(I hope you were looking for advice, if not, apologies )