View Single Post
Bundyo's Avatar
Posts: 4,708 | Thanked: 4,649 times | Joined on Oct 2007 @ Bulgaria
#92
Originally Posted by luca View Post
While threadsafe is the default under windows, It has to be explicitly enabled under unix/linux (as I painfully discovered a while ago when I corrupted a database )
You'll have to check if the option is enabled in the source deb.
If it isn't, no wonder it doesn't work. if it is you can still experience locking problems if various thread try to update the database at once, not really different than having separate processes accessing the same database file, so you should be prepared to manage the case even if you're not programming a multithreaded application (it's just a matter of checking the error code and retrying and/or install a busy handler).
It's all explained in the sqlite documentation.
Yeah, and though threadsafe is enabled in the default sqlite3, even different connection per thread doesn't help. If i handle it myself i can probably fix that. Then again, there might be some problem with the garbage collector and the current sqlite vapi - the sqlite api is quite different than the gobject one.
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.