Case Criteria and Issues
The following table summarizes case criteria and issues.
| Case Specification | Usage Rules |
|---|---|
| UPPERCASE not specified NOT CASESPECIFIC specified |
The following are all equivalent as unique indexes:
|
| UPPERCASE (UC) | Character data is stored in uppercase regardless of the case in which it was typed. Because of the conversion, if a column is defined as UPPERCASE, characters typed as 'aaa' are stored as 'AAA' and therefore are equivalent to 'AAA' when used in a unique index. |
Rules: All Modes
- You can specify the UPPERCASE option in an SQL request to override the stored case specificity assignment for a column.
- If a column is declared to be UPPERCASE, then lowercase letters are converted and stored as their uppercase equivalents.
Note that the KANJI1 server character set only converts the 26 letters a-z to uppercase.
- UPPERCASE supports all letters in the ISO 10646 repertoire.
If you declare a character column to be UPPERCASE and type ‘ά’ (GREEK SMALL LETTER ALPHA WITH TONOS), then that character is translated and stored as ‘Ά’ (GREEK CAPITAL LETTER ALPHA WITH TONOS).
The same applies to the (UC) qualifier.
The following SQL predicate evaluates to TRUE.'ά' (UC) = 'Ά'
- The following data types do not support UPPERCASE
- CLOBs
- UDTs
UPPERCASE Phrase and UPPER Function
The UPPER function is defined by the ANSI SQL:2011 standard and is not the same as declaring a value to be UPPERCASE. For more information, see UPPER in Teradata Vantage™ - SQL Functions, Expressions, and Predicates, B035-1145.