I see what you are suggesting. However, I do not see a schema change going on in the middle of the code that would cause sqlite3_step () to reprepare the statement.
The database that I am working with utilizes sqlite's shared-cache mode for all connections to it along with the sqlite3_unlock_notify ( ) functionality. These connections to the database under shared-cache mode are the same ones that have the tracer attached to them. Could the fact that all the connections attached to the tracer use shared-cache mode be causing this problem? I could not find any mention online of compatibility issues between shared-cache mode and sqlite3_trace (), but I may well have missed them. Thanks so much for the help. -- View this message in context: http://sqlite.1065341.n5.nabble.com/sqlite3-trace-threadsafe-tp64004p64007.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
