I wrote a function to traverse the linked list and print the zSql to stderr.
There was indeed a sql statement being left open by my code! Thats a really usefull debugging technique. I might write an extension to implement this in a more formally. Thanks, Ken [EMAIL PROTECTED] wrote: Ken wrote: > Hi all, > > I'm getting a sqlite error when running sqlite3_close. The error indicates > that there are open statements. > > To the best of my knowledge all statements are closed. I loooked at the > sqlite3_close function and call to close the virtual tables appears to be > causing this issue. > > My question: Are there any means in sqlite to get a listing of what it thinks > are open statements? > There is no published way to do this. If you run in a debugger, you can look at the linked list of "struct Vdbe" objects that sqlite3.pVdbe points to. This is the list of open statements in the current implementation (and subject to change without notice). -- D. Richard Hipp _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
