On Mon, Mar 10, 2014 at 7:36 AM, Staffan Tylen <staffan.ty...@gmail.com>wrote:
> Mike, I've experienced some sporadic problems with database corruptions,
> which I believe has to do with two or more threads sharing the same
> database connection. The PRAGMA compile_options; command shows
> THREADSAFE=1. AFAIK this can mean one of two things: MULTITHREAD or
> SERIALIZED.
>
Hi Staffan,
No, it can only mean 1 thing. It means that SQLite was compiled with the
threading model of SERIALIZED. It would be 2 if the threading model was
MULITITHREADED.
> If no compile option is specified, SERIALIZED should be the default. As I
> have no compile option specified when I compile ooSQLite, I guess it runs
> in serialized mode. But this can be changed using the sqlite_config
> function. So my question is if this is used in ooSQLite somewhere to set a
> different threading mode than serialized?
>
ooSQLite does not change the threading model anywhere. The official
binaries, that is the ones placed on SourceForge, are compiled with
SERIALIZED as the threading model. Nothing is done internally to change
that.
> My thinking is that if serialized is in effect then I should not be able
> to get the problem that I'm facing and I need to look for another
> explanation.
>
Unless you found a bug in SQLite, I think you need to look for another
explanation.
--
Mark Miesfeld
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
