I don't think so. The master journal file is created (and also deleted, unless a crash occurs) during the final commit processing (i.e. during sqlite3_step() of COMMIT). Up until that point there's no special processing for multi-database transactions.
I'm wondering if attaching a database in the middle of a transaction was disallowed purely to save having to test it... Dan. On Wed, 2007-01-10 at 08:37 -0500, Tom Briggs wrote: > Would attaching a database mid-transaction, then making changes in > the newly-attached database, make it impossible to create the correct > master journal file for the overall transaction? Just a curious shot in > the dark. > > -Tom > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Monday, January 08, 2007 10:43 AM > > To: sqlite-users@sqlite.org > > Subject: Re: [sqlite] attach in transaction > > > > [EMAIL PROTECTED] wrote: > > > > > > Can someone tell me why attach cannot be called within transaction? > > > > I do not recall. > > > > Clearly a DETACH will not work inside a transaction if the > > table being detached has been accessed or modified within that > > transaction. But ATTACH could work, I would think. > > > > Perhaps we disallowed ATTACH so that people would not expect > > an automatic DETACH if the transaction rolls back? > > > > The prohibition against running ATTACH within transaction > > first appeared in version 3.0.1. Presumably in version 3.0.0 > > you could ATTACH within a transaction. > > > > If you want to experiement, you can comment out the check > > for begin within a transaction in the attach.c source file, > > recompile, try doing various attaches within transactions, > > and see what bad things happen. This might give us a clue > > as to why it is restricted. Usually we do not prohibit > > things without good reason, I just do not recall what that > > reason is. Perhaps the original reason no longer applies.... > > > > -- > > D. Richard Hipp <[EMAIL PROTECTED]> > > > > > > -------------------------------------------------------------- > > --------------- > > To unsubscribe, send email to [EMAIL PROTECTED] > > -------------------------------------------------------------- > > --------------- > > > > > > ----------------------------------------------------------------------------- > To unsubscribe, send email to [EMAIL PROTECTED] > ----------------------------------------------------------------------------- > ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
