Two decent suggestions in the replies: 1) Set the PRAGMA to case-sensitive, and then use lower() to get insensitivity. 2) Define the column to use case-sensitive collation
For #1 = Set the PRAGMA. then use lower() ----------------------------------------- Is the PRAGMA for case-sensitivity sticky? IOW, does it end up in the DB? (on the road, can't check right now.) If it is, that's good, as long as the DB is R/W, which may not be the case. If it's not, then you have to kick the pragma out every time you open the DB, right? Can I assume it sticks though one DB open/close sequence? For #2 - Define the column as case-sensitive -------------------------------------------- This is good for a new DB. However, the DB may not be your DB. You may not have had the opportunity to define anything. It may have been done by someone else, the DB established, created by an application, etc. You may not have the user privileges to change the R/W status of the original. The acts of defining a DB and using that DB may not be closely coupled in either time or personnel. In a case where the coupling is loose or highly disjoint, you would have to re-create the target column(s) (or the entire DB, if the original is not R/W) with the new definitions. If you don't have control over the original, that could be a significant pushup. Whereas if you could simply say the equivalent of LIKE and ILIKE, there would be no issue at all. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
