For the following examples of CHARACTER data behavior, assume the default server character set is KANJI1 and the table definition for the CASE examples is as follow:
CREATE TABLE table_1 ( i INTEGER, column_l CHARACTER(10) CHARACTER SET LATIN, column_u CHARACTER(10) CHARACTER SET UNICODE, column_j CHARACTER(10) CHARACTER SET KANJISJIS, column_g CHARACTER(10) CHARACTER SET GRAPHIC, column_k CHARACTER(10) CHARACTER SET KANJI1 );
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. For more information, see "KANJI1 Character Set" in Teradata Vantage™ NewSQL Engine International Character Set Support, B035-1125.