JSON Data Type | Character Sets | VantageCloud Lake - Character Sets for the JSON Data Type - 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

You can only use the UNICODE or LATIN character sets with the JSON data type. Other character sets such as GRAPHIC, KANJI1, or KANJISIS are not supported.

In each use of the JSON data type, you can specify the character set using the CHARACTER SET clause. If you do not specify a character set, then the default character set for the user is used.

Character Set Handling

The JSON data type accepts all available session character sets. The data is translated to either the UNICODE or LATIN character set, depending on the definition of the JSON type instance where the data is being used. Therefore, any characters used must be translatable to either UNICODE or LATIN.

Any character set that must be translated is subject to the size restrictions of the UNICODE or LATIN character set. The data in a character set may appear to be the correct size, but when translated to one of the two character sets, the data may be too large and cause a size error.

If the data transformed from a JSON instance must be in a session character set, the database performs the translation, assuming that all of the characters can be translated to that character set.