On 2 Jul 2014, at 5:03pm, Grzegorz Sikorski <g.sikor...@kelvatek.com> wrote:
> I admit I had missed this sentence, but to be honest, it seems to be very > confusing behaviour. I'm glad you have found the problem. It's not good and I don't think this is a good way to handle things. 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. 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. I have no idea what to do about open transactions if their database connection is closed. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
