Re: [sqlite] Effect of using WAL on technical support

Thanks for confirming this. I did some more testing and turned off connection pooling in SQLite.NET and then the connections got closed correctly. I'll plan on rewriting my own connection pool implementation and not using the one provided by the wrapper. Sam On Sun, Apr 10, 2011 at 10:08 PM,

Re: [sqlite] Effect of using WAL on technical support

On 11 Apr 2011, at 2:48am, Richard Hipp wrote: > On Sun, Apr 10, 2011 at 9:36 PM, Samuel Neff wrote: > >> I'm sorry, my statement was misleading. I'm referring to immediately after >> our application is closed. >> >> We're seeing that even if the application is

Re: [sqlite] Effect of using WAL on technical support

On Sun, Apr 10, 2011 at 9:36 PM, Samuel Neff wrote: > I'm sorry, my statement was misleading. I'm referring to immediately after > our application is closed. > > We're seeing that even if the application is gracefully shut down, the -wal > and -shm files are still there.

Re: [sqlite] Effect of using WAL on technical support

I'm sorry, my statement was misleading. I'm referring to immediately after our application is closed. We're seeing that even if the application is gracefully shut down, the -wal and -shm files are still there. In order to clear them I need to open the database files with sqlite3.exe and issue a

Re: [sqlite] Effect of using WAL on technical support

On 11 Apr 2011, at 2:04am, Samuel Neff wrote: > I'm interested in hearing anyone's experiences of using WAL journal mode on > technical support. We often have to copy databases to attach to customer > reports and if the someone were to copy the database file while there is an > active -wal file

[sqlite] Effect of using WAL on technical support

I'm interested in hearing anyone's experiences of using WAL journal mode on technical support. We often have to copy databases to attach to customer reports and if the someone were to copy the database file while there is an active -wal file then we would very likely be missing the most