Default Case Specificity of Character Columns | Teradata Vantage - Default Case Specificity of Character Columns - Advanced SQL Engine - Teradata Database

SQL Data Types and Literals

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-22
dita:mapPath
zsn1556242031050.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1143
lifecycle
previous
Product Category
Teradata Vantageā„¢

Default case specificity varies with mode.

Case specificity does not apply to CLOB types.

ANSI Mode

CHARACTER and VARCHAR data columns defined in ANSI mode are defined as CASESPECIFIC by default. This means that the values 'aa' and 'AA' are not treated as equals.

An option of NOT CASESPECIFIC is implemented to allow columns to be not case specific. NOT CASESPECIFIC is a Teradata extension to the ANSI standard.

Teradata Mode

CHARACTER and VARCHAR data columns defined in Teradata mode (with the exception of character data defined as CHAR or VARCHAR CHARACTER SET GRAPHIC) are defined as NOT CASESPECIFIC by default.

Because Latin characters have canonical representation in all Teradata Database character sets, the effect of the UPPERCASE function is the same for each character set (with the exception of KANJI1, where multibyte characters are not converted to uppercase).

The CASESPECIFIC and UPPERCASE phrases are described in detail in: