Hi -- This is indeed exactly what is happening. On many occasions the mechanism is only interested in the first row of a result set and issues sqlite3_reset() before the result set is completely processed. Given that this is what is occurring, is there any way around this -- essentially, I guess, any way to still have that step statement executed or at least the profile callback invoked? Because at the end of the day, it is the numerous select statements that we probably need to be profiling.
Thanks. Mike -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] 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 <mike.clag...@mathworks.com>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 d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
