Well, to make it binary compatible with existing virtual table implementations, there could be added new function returning const pointer to CollSeq structure from passed index contraint. This function should be callable only from xBestIndex function.
Something like: const CollSeq * sqlite3_vtab_constraint_coll_seq(const sqlite3_index_constraint* pConstraint); sqlite3_index_constraint contains iTermOffset, so to find a collation sequence for it should not be so big problem. How about it? 2013/7/17 Dušan Paulovič <paulo...@gisoft.cz> > But it is the same as with new functions in sqlite3_module. Old SQLite > extensions does not implement xRename function which is now needed. Also, > new feature could be made optional using macro switch like some other > features in SQLite. > > > 2013/7/17 Stephan Beal <sgb...@googlemail.com> > >> On Wed, Jul 17, 2013 at 12:24 PM, Dušan Paulovič <paulo...@gisoft.cz> >> wrote: >> >> > What do you mean? I use it for a while on Windows and all works. >> > Binary not compatible with what? >> > >> >> What Dan means is that libraries built with and without this feature might >> not be binary compatible. i compile against an sqlite3 DLL without this >> feature, then my sysadmin updates libsqlite3 to one with this feature, and >> my binary will then likely segfault at some point (or otherwise invoke >> undefined behaviour) because the binary signatures of the sqlite >> structures >> in my app no longer match those in the library. A recompile of my app >> (with >> no code changes) would be necessary to fix this. >> >> -- >> ----- stephan beal >> http://wanderinghorse.net/home/stephan/ >> http://gplus.to/sgbeal >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
