Update db entry in multiple threads about unqlite-python HOT 6 CLOSED

Is an error or something happening?

For what it's worthy, if you're trying to parallel-ize the actual updating of the database, I don't think you're going to see any benefit over single-threaded. UnQLite is embedded in the Python process and there's no socket I/O operations that would make for good places to do context-switching.

from unqlite-python.

It looks like UnQLite is not thread-safe by default. Check out the "Compile-Time Options" section of the docs:

https://unqlite.org/c_api_const.html

from unqlite-python.

My posted code runs without any unhandled exception thrown. I guess there is no error, but there is no update at all, i.e. not a single database entry gets updated.
I choose this DB, because http://unqlite-python.readthedocs.io/en/latest/index.html states it is thread safe. I need several hundred / thousands concurrent threads. It is not about the speed up, but about different connections that receive timeouts/data on different times.

from unqlite-python.

You're best off probably using a single dedicated thread for writing to the UnQLite database. You can use a queue to have the worker threads push updates to the writer thread...I think that will probably work much better for you.

from unqlite-python.

Of course.
Maybe the thread safety info should be removed from the docs?

from unqlite-python.

I pulled it right from the UnQLite official document on their homepage. It says thread-safe and fully re-entrant. I've created an issue symisc/unqlite#71 which should hopefully clarify.

from unqlite-python.