Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
Sets the case sensitivity of string comparisons in the UltraLite database.
The case sensitivity of data is reflected in tables, indexes, and so on. By default, UltraLite databases perform case-insensitive comparisons, although data is always held in the case in which you enter it. Identifiers (such as table and column names) and user IDs are always case insensitive, regardless of the database case sensitivity. Passwords are always case sensitive, regardless of the case sensitivity of the database.
The results of comparisons on strings, and the sort order of strings, depend in part on the case sensitivity of the database.
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.
You cannot change the case of an existing database. Instead, you must create a new database.
From SQL Central, you can set the case sensitivity in any wizard that creates a database. On the New Database Collation And Character Set page, click the Use Case-sensitive String Comparisons option.
From a client application, set this option as one of the creation options for the CreateDatabase method on the DatabaseManager/ULDatabaseManager class. Pass in case=respect to the creation string parameter of the CreateDatabase method in your programming interface (or case=ignore for a case-insensitive database).