From reading this list, I've learned that for an index to have a change to be used to consume an order by, the collation of the query and the index must match.
But in many instances, that index is one from a virtual table we implement. So is there a way to tell SQLite that vindex is of a given custom collation, to open the possibility of the index being used? FWIW, the collation is a "natural order" one, i.e. a1, a2, ..., a10, ..., a19, a20, ..., a100. Right now the vindex is lexicographic, not "natural order", but of I can have SQLite use it somehow, I can easily change my vindex to "natural order" too. Subsidiary questions: Can one have two indexes on the same column with different collations? And thus have SQLite consider these alternate indexes depending on queries collations? Which goes back to my question about how telling SQLite about a vindex's collation. Thanks, --DD _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
