Truncation of KANJI1 Character Set Fields [Deprecated] - Advanced SQL Engine - Teradata Database

SQL Data Types and Literals

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2021-07-27
dita:mapPath
tpf1598412463935.ditamap
dita:ditavalPath
tpf1598412463935.ditaval
dita:id
B035-1143
lifecycle
previous
Product Category
Teradata Vantage™
In accordance with Teradata internationalization plans, KANJI1 support is deprecated and is to be discontinued in the near future. KANJI1 is not allowed as a default character set; the system changes the KANJI1 default character set to the UNICODE character set. Creation of new KANJI1 objects is highly restricted. Although many KANJI1 queries and applications may continue to operate, sites using KANJI1 should convert to another character set as soon as possible.
It is possible to truncate the output of multibyte characters in an expression with KANJI1 server character set with any of the following client character sets:
  • KanjiEBCDIC
  • KanjiEUC
  • KanjiShift-JIS

In ANSI mode, an error occurs if a non-blank character is truncated.

In Teradata mode, the system returns the number of bytes specified and does not tell you when truncation occurs. The table below shows the hexadecimal returns. The actual return display depends on which system is used.

This character … With this format … Returns this value in hexadecimal … With this character set …
B<AA> 'xx' C20E KanjiEBCDIC
B AA 'xx' 42A3 KanjiEUC