Can you support this notion with the byte code program of the affected 
statement?

In the sqlite shell type

.explain
explain <your query>

and post the output or send it to me off list.

NOTE: I am not an SQLite developer, but will need to upgrade sometime later, so 
getting ahead of possible changes would be helpful.

-----Ursprüngliche Nachricht-----
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im 
Auftrag von Bob Friesenhahn
Gesendet: Mittwoch, 29. März 2017 15:34
An: SQLite mailing list <sqlite-users@mailinglists.sqlite.org>
Betreff: Re: [sqlite] VT table behavior change between 3.10 and 3.17

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


___________________________________________
 Gunter Hick
Software Engineer
Scientific Games International GmbH
FN 157284 a, HG Wien
Klitschgasse 2-4, A-1130 Vienna, Austria
Tel: +43 1 80100 0
E-Mail: h...@scigames.at

This communication (including any attachments) is intended for the use of the 
intended recipient(s) only and may contain information that is confidential, 
privileged or legally protected. Any unauthorized use or dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please immediately notify the sender by return e-mail message and 
delete all copies of the original communication. Thank you for your cooperation.


_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to