On 11/6/07, John Firebaugh <[EMAIL PROTECTED]> wrote: > > You're confusing threads with the context of the connection. When you > > call sqlite3_open() you get a single connection to a db. That > > connection can then be used across threads, but it is for all intents > > and purposes a single line of communication with a database (using it > > twice at the same time doesn't somehow multiply that relationship). > > Thank you for attempting to clarify this for me. You are saying that the > transaction state is part of the connection context, whereas I was > expecting it to be a per-thread-per-connection state.
> What else, besides transaction state, is part of the connection context > and shared with shared connections? I know of the page cache, of which > sharing is desired. Anything else to be aware of? To put things another way: there is no per-thread behavior in SQLite. Everything works on a per-connection basis. (The only new thing is that SQLite is more threadsafe than it was before.) ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
