Indeed SQLite does not care about what the VT implementations xBestIndex routine stuffs in there, as long as the xFilter routine can handle it. AFA SQLite is concerned, this is an opaque value of pointer size.
-----Ursprüngliche Nachricht----- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Ben Manashirov Gesendet: Dienstag, 03. Juli 2018 02:47 An: sqlite-users@mailinglists.sqlite.org Betreff: [EXTERNAL] [sqlite] documentation for sqlite3_index_info-ídxStr typo. https://www.sqlite.org/c3ref/index_info.html Instead of referring to idxStr there is text that talks about idxPtr. It should mention if idxStr must point to a valid string or can it point to arbitrary data. If the latter than idxStr type should change to void* perhaps. Reading this doc it sounds like idxStr can point to anything and sqlite will treat it as arbitrary data instead of a string. Happy Canada Day :) Ben Manashirov _______________________________________________ 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 | Klitschgasse 2-4, A-1130 Vienna | FN 157284 a, HG Wien, DVR: 0430013 | (O) +43 1 80100 - 0 May be privileged. May be confidential. Please delete if not the addressee. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
