Hello, Richard, I thought that after a transaction SQLite opened and closed the DB anyway and that was one of the main reasons for using a transaction where many separate updates are taking place it cuts down the opening and closing so only one occurs?
This problem might be an index problem? Kinda sounds like it. Can you isolate it down to insert or updates that are taking longer? Or are both taking twice as long? regards Greg O ----- Original Message ----- From: "D. Richard Hipp" <[EMAIL PROTECTED]> To: "Dennis Cote" <[EMAIL PROTECTED]> Cc: "sql-users" <[EMAIL PROTECTED]> Sent: Wednesday, March 03, 2004 3:10 AM Subject: Re: [sqlite] A puzzling SQLite slowdown > Dennis Cote wrote: > > > > Are you suggesting that SQLite is not enabling these optimizations, or that > > my code needs to do something different to enable them? > > > > The optimizations should be enabled automatically. You shouldn't have > to do anything. Perhaps the problem is that a bug in SQLite is preventing > the automatic enabling. > > Remember, this is a *wild guess*. > > > -- > D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
