Default Case Specificity of Character Columns | VantageCloud Lake - Default Case Specificity of Character Columns - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
Language
English (United States)
Last Update
2024-04-03
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

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. Therefore, 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 VantageCloud Lake 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: