|
The results of comparisons on strings, and the sort order of strings, in part depends on the case sensitivity of the database. Case sensitivity in UltraLite databases affects:
Data The case sensitivity of the data is reflected in indexes and in string comparisons. By default, comparisons are always case insensitive. For example, UltraLite compares short sleeve t and Short Sleeve T equally.
Identifiers Identifiers include table names, column names, and so on. Identifiers, including user IDs, are always case insensitive, regardless of the database case sensitivity. For example, UltraLite always compares UID=DBA and UID=dba equally.
Passwords Passwords are always case sensitive in UltraLite databases. For example, UltraLite does not compare PWD=sql and PWD=sQl equally.
There are some collations where particular care is required when assuming case insensitivity of identifiers. In particular, Turkish collations have a case-conversion behavior that can cause unexpected and subtle errors. The most common error is that a system object containing a letter I or i is not found.