-----Ursprüngliche Nachricht----- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Cezary H. Noweta Gesendet: Mittwoch, 29. März 2017 12:37 An: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Betreff: Re: [sqlite] VT table behavior change between 3.10 and 3.17
Hello, On 2017-03-29 10:48, Hick Gunter wrote: > According to the documentation of Virtual Tables and Opcodes: > [...] > xOpen( table, cursor) is called to announce that SQLite intends to > read from a table. A cursor cannot be used to write to a table. Do > whatever is necessary to read from the backing store and set any VT > implementation specific fields in the cursor structure (e.g. a file > handle enabled for reading) Where have you taken above fragment from? The doc says: ``The xOpen method creates a new cursor used for accessing (read and/or writing) a virtual table.'' -- at least from 3.8.5 until now. It is not the best to rely on the assumption that xOpen-ed cursor is read-only, or have I missed something? Why xOpen-ed cursor cannot be used to write to a table? -- best regards Cezary H. Noweta 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. ___________________________________________ 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
