"Roger Binns" <[EMAIL PROTECTED]> wrote: > > If you call sqlite3_enable_shared_cache while > > another connection is open, you will get an > > SQLITE_MISUSE error. But you can ignore that > > error if you want. > > The doc is far scarier: > > This routine must not be called when any database > connections are active in the current thread. Enabling > or disabling shared cache while there are active database > connections will result in memory corruption. > > >From what you said it sounds like changing the setting > while connections are active will cause corruption, > but calling the api and setting it to what it already > is will give SQLITE_MISUSE.
Changing the setting while a session is active will lead to serious problems. That's why I added a check for that behavior that makes the routine return SQLITE_MISUSE instead. > > Is the shared cache known to be bug free? > I am not aware of any bugs in the code. This doesn't mean there aren't any. -- D. Richard Hipp <[EMAIL PROTECTED]>
