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, Simon Slavin <slav...@bigfraud.org> wrote: > > On 11 Apr 2011, at 2:48am, Richard Hipp wrote: > > > On Sun, Apr 10, 2011 at 9:36 PM, Samuel Neff <srneff.li...@gmail.com> > 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. In order to clear them I need to open > the > >> database files with sqlite3.exe and issue a "pragma wal_checkpoint". > > > > The -wal and -shm are deleted when the last connection to the database > > closes. If you are having -wal and -shm files left over, that implies > that > > you are not closing all your database connections before you exit. > > Yes ! If your application has exited and you still have a journal file, > something is wrong. Are you closing your connection correctly, however > ASP.NET wants you to do it ? > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
