On Sun, Aug 7, 2011 at 5:02 PM, Simon Slavin <[email protected]> wrote:
> > Can you explain what happens? > > I'm sorry but I can't. But SQLite is designed to need sqlite3_close() > (and, in fact, sqlite3_shutdown()) so it's probably best to do them. > > Not it isn't - at least not from a database integrity point of view. sqlite3_close() is needed to avoid memory leaks, but that isn't what is at issue here. As far as the database file on disk is concerned, each transaction is an isolated event. And the database file on disk does not know or care if the current transaction is using the same database connection as the previous, or if there was an sqlite3_close() in between, or if it is coming from a completely separate process. So I don't think sqlite3_close() is the issue. But beyond that, I don't have any ideas, other than the ones previously mentioned on the "howtocorrupt" webpage. -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
