You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Why don't you use: SELECT ... WHERE field=UPPER('value') ... ORDER BY field, if you store uppered values in fields...
or
2. Use computed index:
CREATE INDEX INDEX_NAME ON TABLE COMPUTED BY (UPPER(FIELD))
and then
SELECT ... WHERE UPPER(field)=UPPER('value') ... ORDER BY UPPER(field)
works fine.
Submitted by: Stefan Schmaltz (schlocke)
Votes: 1
We have a Database with UNICODE_CI and all varchar field have an Index.
So when executing
SELECT ...WHERE field='value' ... ORDER BY field
the result is fast
but when executing
SELECT ... WHERE UPPER(field)=UPPER('value') ... ORDER BY UPPER(field)
the result is very slow.
Suggestion: Case Insensitive Index should ignore UPPER (AND LOWER) because there is no difference
The text was updated successfully, but these errors were encountered: