Not sure what you mean so I'll assume you are thinking of string comparisons in SQL.
All string comparisons I've tested become case insensitive with a database that uses TERRITORY_BASED:SECONDARY collation. I've tested the following name LIKE 'a%' matches both "Adam" and "adam" name = 'adam' matches both "Adam" and "adam" name BETWEEN 'a' AND 'c' matches both "Baker" and "baker" name >= 'a' AND name <= 'c' matches both "Baker" and "baker" JOIN's also compare case insensitively. -Gunnar geoff hendrey (JIRA) wrote: > Could you provide a synopsis of the recommended way to do case insensitive > string comparison, taking into account this new capability you added? >
