Re^2: "Can't use index" with DBD::SQLite

Thanks. I ran your code, and it worked for me, and then re-created my index per your specifications, with the one tweak I made before. It still didn't work on my table. So I figured that tweak must be the problem.

For some reason I don't understand, it didn't like my COLLATE NOCASE DESC specification. When I re-created the index once again without that, it started working. Huh.

Comment on Re^2: "Can't use index" with DBD::SQLite

Replies are listed 'Best First'.
Re^2: "Can't use index" with DBD::SQLite by zyxsys.com (Initiate) on Mar 01, 2013 at 10:24 UTC
When you give the COLLATE NOCASE DESC option in the index it means convert all the text to lower case and store them in descending order for case insensitive search. So, to make use of that index, you have to give the same collation again in your query, and the following should work. `SELECT profile_id FROM profile INDEXED BY idx_name WHERE name == ? COL +LATE NOCASE` [download] If you recreated the index without this collation, then it means you cannot do case insensitive search, or have to convert things to upper or lower case every time like below. `SELECT profile_id FROM profile INDEXED BY idx_name WHERE lower(name) = += lower(?)` [download] Although you have found a workaround, this may be useful for someone else, facing a similar problem.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: "Can't use index" with DBD::SQLite
by zyxsys.com (Initiate) on Mar 01, 2013 at 10:24 UTC

When you give the COLLATE NOCASE DESC option in the index it means convert all the text to lower case and store them in descending order for case insensitive search. So, to make use of that index, you have to give the same collation again in your query, and the following should work.

SELECT profile_id FROM profile INDEXED BY idx_name WHERE name == ? COL
+LATE NOCASE
[download]

If you recreated the index without this collation, then it means you cannot do case insensitive search, or have to convert things to upper or lower case every time like below.

SELECT profile_id FROM profile INDEXED BY idx_name WHERE lower(name) =
+= lower(?)
[download]

Although you have found a workaround, this may be useful for someone else, facing a similar problem.

[reply]
[d/l]
[select]