Great. Thank you. I will visit with our API guy to see if it's any extra burden for him to issue a SQLITE_DONE. Also a colleague just informed me that I can possibly suppress a lot of the TRANSACTION activity I am seeing by issuing an a BEGIN and COMMIT TRANSACTION myself. He suspects that some kind of Auto Transaction behavior is kicking in or that even if that isn't the case, that if a transaction is in progress it will just be joined rather than having multiple transaction scopes. So I will play with this.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Richard Hipp Sent: Thursday, October 24, 2013 9:40 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Trying to figure out how to circumvent sqlite3_win32_mbcs_to_utf8 On Thu, Oct 24, 2013 at 9:06 AM, Mike Clagett <[email protected]>wrote: > Hi -- > > I finally got a chance to put in the profiling and trace callbacks. Very > interesting stuff, which I am attempting to analyze. One of the things I > am seeing is that none of the SELECT statements that show up in the > trace actually are being captured by the Profiling callback. > The profile callback is invoked during the sqlite3_step() call that returns SQLITE_DONE. Perhaps your queries are returning multiple rows of result, but you are only looking at some prefix of those rows before you invoke sqlite3_reset() or sqlite3_finalize()? In that case, no sqlite3_step() call would ever return SQLITE_DONE and so the profile callback would never be invoked. -- D. Richard Hipp [email protected] _______________________________________________ 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
