On Wed, 29 Mar 2017, Hick Gunter wrote:
To avoid anomalies when changing "key fields", SQLite will scan through the whole cursor first, saving the rowids and new contents of the record(s) satisfying the WHERE clause. It will then close the cursor and call xUpdate for the affected records. The main sequence is: xBegin() - xOpen() - xFilter() - xNext()... - xClose() - xUpdate()... - xSync() - xCommit()
If this is supposed to be the case, then it seems that xClose() is not being called before xUpdate() with 3.17.
The problematic virtual table module seems to be improperly constructed and was implemented based on observed behavior at the time. There is inadequate tracing in the code so proper tracing will be added when it is re-written.
Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
