-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Virgilio Alexandre Fornazin wrote: > A good and new safe could be a sqlite3_close_v2() call prototyped like > > int sqlite3_close_v2(sqlite3 * db, int closePendingStatements);
Funnily enough that is exactly what I provide in my Python wrapper for SQLite! Reference counting ensures that the sqlite3_db can't be freed before all the statements are closed but the above method is a quick way for the developer to proactively close everything. Having a close_v2 is most likely the best solution since there won't be semantics changes over what people have already developed. It can also ensure the right thing happens when threads are being abused. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIKlSymOOfHg372QQRAiEbAJ9mbFpensXkTXmJtI90vPfTqMNpswCgmh2/ 2HwZvkW8FdDUzWId2mtE5fs= =oawA -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
