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 .. 222 223 224 225 226 227 < 228 > 229 230 231 232 233 234 .. 241 >> Next

Code Set 2 Not permitted
Code Set 3 First byte: 0x8F JIS-x0212
(three bytes) Second and Data must be entered in
third bytes: A1-FE an even number of
logical cs3 characters

KanjiEUC sessions should not submit a name or data character with the client encoding of 0x0E or 0x0F.

These values are reserved internally for the KanjiEBCDIC Shift-Out and Shift-In characters, which indicate multibyte character mode.

The stored result will confuse the internal uppercase conversion function, which can affect the retrieval of data using non-case specific comparisons; for example, the data may not be found.

The valid ranges for JIS-x0201 characters in KanjiEUC object names can be found in rows cs0 and cs2 in the EUC Code Set Localization table, in Chapter 4, in the “Character Ranges” section. Note that Katakana symbols 0x8EA1 - 0x8EA5 and Latin symbols other than $, #, and - are not allowed.

G-50

Teradata RDBMS for UNIX SQL Reference
International and Japanese Character Support

DOS/V-Compatible Character Set (KanjiShift-JIS_0S)

DOS/V-Compatible Character Set (KanjiShift-JIS_0S)

In this document, the term KanjiShift-JIS is used to refer to the IntroductioH DOS/V-compatible character set (KANJISJIS_0S).

This supports the encoding of mixed single byte character/multibyte character data used on PC platforms running DOS/V Windows (Japanese DOS), single byte character Hankaku Katakana characters, and double byte Kanji characters.

The tables below present the KanjiShift-JIS data validity criteria.

KanjiShift-JIS Character Data Validity Criteria

Character Constraint Range Note
single byte 0x00-0x7F or JIS-x0201
character 0xA1-0xDF
multibyte First byte: 0x81-0x9F or 0xE0-0xFC JIS-x0208
character Second byte: 0x40-0x7E or 0x80-0xFC

KanjiShift-JIS Graphic Data Validity Criteria

Character Constraint Range Note
0x0000 Graphic pad
character
multibyte First byte: 0x81-0x9F or 0xE0-0xFC JIS-x0208
character Second byte: 0x40-0x7E or 0x80-0xFC

KanjiShift-JIS sessions should not submit a name or data character with the client encoding of 0x0E or 0x0F.

These values are reserved internally for the KanjiEBCDIC Shift-Out and Shift-In characters, which indicate multibyte character mode.

The stored result will confuse the internal uppercase conversion function, which 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-51
International and Japanese Character Support

Japanese Character Translation and Storage

Japanese Character Translation and Storage

Each Japanese character has a logical form and a physical form. Its logical form is its shape, or visual representation. Its physical form is the byte configuration needed to electronically represent its logical form.

The Teradata RDBMS translates single byte characters from the client (external) encoding to internal encoding during input, and back to client encoding during output.

The Teradata RDBMS translates single byte characters, (for example, simple Latin letters, digits (0-9), the symbols dollar sign ($), number sign (#), and underscore (_)), into canonical form.

The internal single byte character encoding is based on the JIS-x0201 standard. See Figure H-1 in Appendix H, “Japanese Character Sets.” In order to accommodate the translation of all KanjiEBCDIC single byte characters, the Teradata RDBMS includes extensions to JIS-x0201, as shown in the following table.

Teradata RDBMS Extensions to JIS-x0201

Character Description Hexadecimal Value
? (cent sign) 0x10
? (pound currency symbol) 0x11
- (IBM logical NOT sign) 0x12
\ (backslash) 0x13
~ (tilde) 0x14

Under this character set . . . These characters . . . Are . . .
KanjiEBCDIC all multibyte stored without translation Shift-Out and Shift-In are translated, but to the same encoding (0X0E and 0x0F, respectively)
KanjiShift-JIS all multibyte stored without translation

G-52

Teradata RDBMS for UNIX SQL Reference
International and Japanese Character Support

Japanese Character Translation and Storage

Under this character set . .

These characters .

Are . .

KanjiEUC

some

translated.

The four code sets are handled as follows:

Code Set Translation
cs0 all characters, from EUC to the internal representation (based on JIS-x0201) and stored as single byte characters
cs1 character data only, from EUC to Shift-JIS. Graphic data is stored without translation.
cs2 character data only, the first byte (ss2=0x8E) is translated to 0x80; the second byte is left unmodified.
cs3 character data only, the first byte (ss3=0x8F) is translated to 0xFF; the remaining two bytes are left unmodified. Graphic data is stored without translation.

Teradata RDBMS for UNIX SQL Reference

G-53
International and Japanese Character Support

Accessing and Sharing Japanese Character Objects and Data

Objects Accessible Across Character Sets
Previous << 1 .. 222 223 224 225 226 227 < 228 > 229 230 231 232 233 234 .. 241 >> Next