15.10 - Character Set Handling - Teradata Database

Teradata Database Teradata JSON

Product
Teradata Database
Release Number
15.10
Published
December 2015
Language
English (United States)
Last Update
2018-06-05
dita:mapPath
TeradataJSON_15_10.ditamap
dita:ditavalPath
ft:empty

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 some character sets may appear to be the correct size, but when translated to one of the two character sets, the data may be too large and result in a size error.

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