The CHARSET_COLL collation produces a binary ordering based upon the current client character set. The NOT CASESPECIFIC version is designed to produce the results if the strings were converted to uppercase and then sorted in binary order on the client.
CHARSET_COLL gives you a collation that matches the client character set. For example, if the client character set is KANJIEBCDIC5035_0I, then the collation matches KANJIEBCDIC5035_0I order (rather than EBCDIC order).
Strings are compared character-by-character.
The comparison rules for CHARSET_COLL are:
KANJI1 character data can contain mixed single-byte/multibyte characters. Single-byte characters are translated into the Teradata Database form-of-use and multibyte characters are not translated.
The distinction between this and a binary sort on the client is that the JIS X 0208 characters collate before, rather than after, the JIS X 0212 characters.
You can specify CHARSET_COLL as the default user collation with the CREATE USER or MODIFY USER statements.
You can also use the SQL SET SESSION COLLATION CHARSET_COLL statement to override any user defaults.
For information on... |
See... |
Teradata Database collating conventions
|
“Comparison Operators” and “Comparisons for KANJI1 Characters” in SQL Functions, Operators, Expressions, and Predicates |
“ORDER BY Clause” in SQL Data Manipulation Language |