Aaah... I only read the documentation in sqlite3.h.
Thanks for the tip. Pontus ________________________________ Från: Simon Slavin <slav...@bigfraud.org> Till: Pontus Bergsten <pontus_bergs...@yahoo.se>; General Discussion of SQLite Database <email@example.com> Skickat: torsdag, 21 juni 2012 13:46 Ämne: Re: [sqlite] Problem with concurrent transaction and DETACH DATABASE On 21 Jun 2012, at 9:53am, Pontus Bergsten <pontus_bergs...@yahoo.se> wrote: > were it was stated that > > "You should be in the habit of calling sqlite3_reset() on each query as soon > as that query finishes. Otherwise the query *might* leave a read-lock on the > database file and thus prevent subsequent write operations for working > correctly." > > I suppose that the "*might* locking part" should be explicitly stated in the > SQLite API documentation for step/reset. The documentation for the use of statements has it: <http://www.sqlite.org/c3ref/stmt.html> It doesn't tell you what will go wrong if you don't use _finalize() but it does tell you when to use _reset() and that you must use _finalize(). Simon. _______________________________________________ sqlite-users mailing list firstname.lastname@example.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users