> > I would have expected the "no transaction > > nesting" restriction to be enforced per-thread, not per-connection. > > And what made you believe so? How is supporting nested transactions in
> multiple threads any easier than supporting them in a single thread? I have no idea; the main attraction of SQLite is it frees me from having to worry about such difficulties. From a _user's_ perspective, rather than an implementer's perspective, it seems a reasonable assumption: "Restrictions on the use of the same database connection by multiple threads have been dropped. It is now safe for multiple threads to use the same database connection at the same time." This suggests to me that operations that can be accomplished using per-thread database connections (e.g. a transaction on each thread) can now be accomplished with a single database connection. Obviously two threads can issue commands that change the database at the same time, which in the absence of a "begin transaction" statement, still uses an (autocommitted) transaction. So from that perspective it also seems reasonable to expect explicit transactions to work just as well. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
