Hrm... I didn't realize that #define was limited to values less than 32. That being the case, you probably can't avoid starting multiple transactions.
-Tom > -----Original Message----- > From: Serena Lien [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 04, 2006 9:57 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Optimize performance - reading from > multiple database files, processing and writing to separate > results database file? > > Yes, I could indeed determine which databases I want to > attach to, but there > is a limit to the number of databases you can attach (I think > it's 32?) and > I might have more than that. So I thought the safer route was > to attach as I > go.. > > Serena. > > > On 10/4/06, Tom Briggs <[EMAIL PROTECTED]> wrote: > > > > > > Do you know all of the databases that you want to attach > to at the > > start of processing? If so, there's no reason you can't > simply attach > > them all beforehand, start your transaction, and complete all your > > processing. If you have to decide dynamically, based on > the data, which > > databases you'll need, then you have no choice but to start and end > > multiple transactions in order to attach the databases as you go. > > > > -Tom > > > > > ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
