- If expression_1 and expression_2are of different lengths, the shorter string is padded with enough pad characters to make both the same length.
-
Session mode is identified.
In this mode … The default case specification for a character string is … ANSI CASESPECIFIC. Teradata NOT CASESPECIFIC. Unless the CASESPECIFIC qualifier is applied to one or both of the expressions, any simple Latin letters in both expression_1 and expression_2 are converted to uppercase before comparison begins.
To override the default case specification of a character expression, apply the CASESPECIFIC or NOT CASESPECIFIC phrase.
- Characters identified as single byte characters under the current character set are converted according to the collation sequence in effect for the session.
-
For the KanjiEUC character set, the ss3 0x8F character is converted to 0xFF. This means that a user-defined KanjiEUC codeset 3 is not properly ordered with respect to other KanjiEUC code sets.
The ordering of other KanjiEUC codesets is proper; that is, ordering is the same as the binary ordering on the client system.
- The prepared strings are compared and trailing pad characters are ignored.
- EBCDIC
- ASCII
- MULTINATIONAL
- CHARSET_COLL
- JIS_COLL
Collation can be set at the user level with the COLLATION option of the CREATE USER or MODIFY USER statements, and at the session level with the [[.]SET] SESSION COLLATION statement or the CLIv2 CHARSET call.
If the MULTINATIONAL collation sequence is in effect, the collation sequence of a Japanese language site is determined by the collation setting installed during start-up.