On Sunday, 12 February, 2017 07:28, Brian Macy <[email protected]> said:
> Recently I removed a bunch of latency from my application. Suddenly I’m > getting odd errors where a record that was just inserted can’t be read by > the same process. SQLite does not do "per process" locking/transactions -- it does locking/transactions/isolation per connection (handle returned by one of the sqlite_open* calls). You are not "spawning" new processes using the same connection handle, are you? > In fact, even waiting till completion of the run, the > record never exists. I confirmed the insert is getting called with the > correct parameters, I logged everything coming back on the error log > callback, and I verified that the DB is always in auto commit. Again, autocommit is not per database (nor per process) but is per connection. Does the database connection close properly (return SQLITE_OK)? _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
