On Wed, 2 Jul 2014 17:18:23 +0100 Simon Slavin <slav...@bigfraud.org> wrote:
> I hope SQLite4 changes this and if there are statements still open > either returns an error code or automatically closes any open > statements. Or both. Me too. I can't think of any other application I use that doesn't free all resources associated with a handle. The analog in the OS might be write(2) working after close(2) is called on the descriptor, instead of EBADF. > It would also be nice if there was an API call you could make on a > database handle which would return the number of statements which > were open on that database. Yes, and a list of statement handles. I would represent them as a table, perhaps MASTER_STATEMENTS. > I have no idea what to do about open transactions if their database > connection is closed. Rollback, no? Same as if kill -9 were called on the application. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
