Nathan, On Tue, Dec 13, 2016 at 8:36 PM, Nathan Bossett <[email protected]> wrote: > On Tue, Dec 13, 2016 at 08:20:44PM -0500, Igor Korot wrote: >> > What more are you trying to find out? >> >> If I forget to finalize statement, I can use that sequence to find >> which query is dangling. >> >> So are you saying that this code should be executed if sqlite3_close() >> didn't return SQLITE_OK? > > I'm saying that your code should be trying to shut down gracefully > before calling close: finalize statements and whatever else.
I understand that. That's why I'm trying to find out if everything is OK... > > If I get to a point in my code where I know I haven't done that > because the sqlite3_close() fails, then I don't have too many > intelligent options left other than to note the problem. > > So I'm not sure exactly why you're trying to create an additional > statement: once you know the close succeeded or failed, what more > are you trying to learn? If all you want to know is that bare fact > further down in the code, create a bool db_is_open or set the db > pointer. Because if graceful closure is not possible because of me I want to know right away so that I can fix the problem. Thank you. > > -Nathan > _______________________________________________ > sqlite-users mailing list > [email protected] > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
