Richard, Well, that has been the whole point of this discussion.
I have code which creates a transaction on a connection in the parent thread, then creates several child threads which attempt to use the same connection and transaction in a synchronised mannor. It does not work, and by all the documentation that i have read on sqlite, it should not work. Ive also tried allocating a separate transaction to each child thread, but of course then they all lock each other out. So the only workable alternative has been to either use much slower fine grained transactions within each child thread, or to use an in process server which performs all operations on one thread (at what i presume to be a considerable hit to performance). On 12/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
"Emerson Clarke" <[EMAIL PROTECTED]> wrote: > Even on the > platforms where a single sqlite3 * structure can be used on multiple > threads (provided it is not at the same time), it is not possible to > have a transaction which works across these threads. I beg to differ. What makes you think this does not work? -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
