Plus, of course, index will only ever be used for operations where you have overridden the default collating sequence for the operation, for example by specifying collate nocase in the join expression, or adding the collate nocase to the order by or group by.
> -----Original Message----- > From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users- > boun...@sqlite.org] On Behalf Of Simon Slavin > Sent: Monday, 2 September, 2013 06:48 > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Query problems > > > On 2 Sep 2013, at 8:25am, Eduardo Morras <emorr...@yahoo.es> wrote: > > > Or create the index with collate > > > > CREATE INDEX idx_collated_column ON myTable ( column COLLATE NOCASE ) > > The problem with doing it in the index is that it's hard to predict when > SQLite will use a particular index. Better to think about the nature of > your data when you create the table. > > On the other hand if you have already created your table and have lots > of foreign keys it can be a pain to try to reconstruct your data by > DROPping and recreating tables. It may be easier just to add a new > index. > > Simon. > _______________________________________________ > 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
