> [...] Why xOpen-ed cursor cannot be used to write to a table? > The xUpdate method alone is used to perform updates to virtual tables. > It does not take a cursor argument.
> Also, there is no method taking a cursor argument that allows data to be > changed. > The documentation is correct in that UPDATE and DELETE queries involve > reading from the table first, and xOpen will be called to do that. > Pure INSERT queries don't even call xOpen. Indeed, the sole place, where VOpen is used, is a processing of WHERE clauses (UPDATE, DELETE have a WHERE clause, while INSERT, REPLACE have not). My questions concerned a connection between your first sentence (``According to the documentation...'') and the remaining part of your post. Now, I see that you have explained the behavior of SQLite rather then quoted the documentation. I'm sorry for OT disturbance. -- best regards Cezary H. Noweta ----- No problem, take it as a digest of the documentation enhanced by the experience of writing several VT implementations. Most of which, BTW, don't care about transactions but apply changes immediately, using xCommit/xRollback only as a hint that the backing store may now be "closed" if applicable (e.g. file-based VT). This is because we use SQLite mainly as a query tool and data store integrity is maintained by the application itself. Catastrophic failures are repaired via restore of a checkpoint and rollforward of the transaction log. ___________________________________________ 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
