Hi,
I am using WAL. If I use a new db connection for every write (as usually suggested practice) and connection pooling is enabled, my writes are quite a bit faster. Good so far. However, I also see some db locks occurring, specifically: (517) SQLITE_BUSY_SNAPSHOT For some reason, the .net wrapper only traces that to the console, but it does not throw. 1) How can I make the sqlite .NET wrapper throw an exception so I can deal with it. 2) Retry the same write again. Ideally, SQLite should retry itself, but I am not sure if this is supported. Thanks Andy _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
