"Igor Tandetnik" <[EMAIL PROTECTED]> wrote: > > MS SQL also supports defining multiple indexes on the same table and > field(s), differing only in collation (and the optimizer is smart > enough, most of the time, to use these indexes appropriately). I haven't > tried it with SQLite, maybe it's also supported. >
SQLite also supports multiple indices differing only in collation, and the optimizer will use the appropriate index to satisfy the ORDER BY clause. But because the SQLite parser does not currently provide a means to change the collating sequence assigned to an expression, there is no way for the optimizer to use different indices for optimizing access since an expression in the WHERE clause can only have a single collation. That's what I'm trying to fix.... -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
