Books
in black and white
Main menu
Share a book About us Home
Books
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics
Ads

Teradata RDBMS forUNIX SQL Reference - NCR

NCR Teradata RDBMS forUNIX SQL Reference - NCR, 1997. - 913 p.
Download (direct link): teradataforunix1997.pdf
Previous << 1 .. 221 222 223 224 225 226 < 227 > 228 229 230 231 232 233 .. 241 >> Next


CCSID=13218 single byte character data)

CCSID=4836 (mixed single byte character/multibyte character data)

GCCSID=4396 (graphic data)

Under this character set, a CHARACTER data type supports only mixed single byte characters/multibyte characters. Accepted characters include simple uppercase Latin letters, digits, and other SQL terminal symbols; single byte character Hankaku Katakana symbols, double byte Kanji characters, and various other characters.

Note that this character set has no encoding for lowercase Latin letters.

Teradata RDBMS for UNIX SQL Reference

G-45
International and Japanese Character Support

KANJIEUC_0U

KANJIEUC_0U

This character set emulates the single byte character/multibyte character encoding of the Japanese Extended UNIX Code. The codesets are as follows:

Codeset 0 (cs0)

Supplementary codeset 1 (ss1)

Supplementary codeset 2 (ss2)

Supplementary codeset 3 (ss3)

This character set accepts simple uppercase and lowercase Latin letters, digits, and other SQL terminal symbols; Zenkaku Katakana; Hankaku Katakana; double byte Kanji characters, and various other characters.

G-46

Teradata RDBMS for UNIX SQL Reference
International and Japanese Character Support

KANJISJIS_0S

KANJISJIS_0S

This character set emulates the Shift-JIS encoding (DOS Kanji) used by PC clients running DOS/V Windows. It accepts simple uppercase and lowercase Latin letters, digits, and other SQL terminal symbols; single byte character Hankaku Katakana; double byte Kanji characters, and various other characters.

Mixed single byte character/multibyte character strings must have matching Shift-Out/Shift-In characters to delimit the start and end of the multibyte character substring.

The tables below present the KanjiEBCDIC data validity criteria as found in the Teradata RDBMS.

Table G-3

KanjiEBCDIC Character Data Validity Criteria

State Constraint Range Note
single byte character 0x00-0x0D; 0x0F-0xFF All except Shift-Out (0x0E)
multibyte characters (within Shift-Out and Shift-In delimiters) (1) First byte: 0x41-0x7F Second byte: 0x41-0xFE (2) 0x4040 character (3) 0xFEFD or 0xFEFE character

Table G-4

KanjiEBCDIC Graphic Data Validity Criteria

State Constraint Range Note
0x0000 Graphic pad character
multibyte character (1) First byte: 0x41-0x7F Second byte: 0x41-0xFE (2) 0x4040 character (3) 0xFEFD or 0xFEFE character

KanjiEBCDIC users should not submit name or data characters with the client encoding indicated below, because the stored result will confuse the uppercase conversion function. This can affect the retrieval of data using non-case specific comparisons; for example, the data may not be found.

Teradata RDBMS for UNIX SQL Reference

G-47
International and Japanese Character Support

KANJISJIS_0S

Data should not contain a single byte character with the client encoding of 0x80 or 0xFF. These values are translated into the internal encoding for the ss2 and ss3 escape characters of KanjiEUC data.

Data should not contain non-printable characters. A non-printable character might be translated internally into a byte with the most significant bit turned ON. According to the EUC and Shift-JIS standards, these characters are multibyte characters and thus are not converted to uppercase for comparison and sorting operations.

G-48

Teradata RDBMS for UNIX SQL Reference
International and Japanese Character Support

UNIX-Compatible Character Set (KanjiEUC_0U)

Introduction

KanjiEUC Character Data Validity Criteria

KanjiEUC Graphic Data Validity Criteria

UNIX-Compatible Character Set (KanjiEUC_0U)

In this document, the term KanjiEUC is used to refer to the Unix-compatible character set (KANJIEUC_0U).

Externally, KanjiEUC has four encodings, as follows:

Code Set 0 (single byte character)

Code Set 1 (two-byte character)

Code Set 2 (two-byte multibyte character with first byte

ss2=0x8E)

Code Set 3 (three-byte multibyte character with first byte

ss3=0x8F)

The KanjiEUC character set supports standard EUC single byte and multibyte characters, Zenkaku Katakana, Hankaku Katakana, and double-byte Kanji characters. The tables below present the KanjiEUC data validity criteria.

State Constraint Range Note
Code Set 0 0x00-0x7F JIS-x0201 + table G-10 indicates most of U.S. ASCII.
Code Set 1 (two bytes) First byte: Second byte: 0xA1-0xFE 0xA1-0xFE JIS-x0208
Code Set 2 (two bytes) First byte: Second byte: 0x8E A1-DF JIS-x0201 Hankaku Katakana
Code Set 3 (three bytes) First byte: Second and third bytes: 0x8F A1-FE JIS-x0212

State Constraint Range Note
Code Set 0 Not permitted
Code Set 1 0x0000 Graphic pad character
Code Set 1 First byte: 0xA1-0xFE JIS-x0208
(two bytes) Second byte: 0xA1-0xFE

Teradata RDBMS for UNIX SQL Reference

G-49
International and Japanese Character Support

UNIX-Compatible Character Set (KanjiEUC_0U)

State Constraint Range Note
Previous << 1 .. 221 222 223 224 225 226 < 227 > 228 229 230 231 232 233 .. 241 >> Next