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 .. 209 210 211 212 213 214 < 215 > 216 217 218 219 220 221 .. 241 >> Next

3 Optionally assign a default character set to each host.
4 Install the character set.

Teradata RDBMS for UNIX SQL Reference G-7
International and Japanese Character Support

Defining Character Sets

5 Optionally, assigning a default character set to each host.

6 Installing the character set.

Note: For Japanese character sets, only single byte characters can be defined individually. Multibyte characters are defined via a naming convention for the character set as described in “Naming User-Defined Kanji Character Sets”.

G-8

Teradata RDBMS for UNIX SQL Reference
International and Japanese Character Support

User-Defined Character Set Restrictions

User-Defined Character Set Restrictions

User-defined character set restrictions that apply for EBCDIC and Intr0ducti0n ASCII clients are described in the following sections.

One general restriction is that the character set name cannot be one of the predefined Kanji character set names, such as

• EBCDIC

• KATAKANAEBCDIC

• KANJIEBCDIC5026_0I

• KANJIEBCDIC5035_0I

• KANJISJIS_0S

• KANJIEUC_0U

See also the section below, “Naming User-Defined Kanji Character Sets”.

EBCDIC

User-defined character sets based on the EBCDIC character set cannot redefine a certain subset of the EBCDIC character set. This subset of characters set aside as required EBCDIC characters is identified as shaded code points in Figure G-1.

The shaded code points must remain as defined, and the user-defined translation tables must map these code points into the correct internal Teradata RDBMS representations.

ASCII

User-defined character sets based on the ASCII character set must preserve the definition of codepoints 0-127. This means that you may only redefine those characters whose numeric value is 128 or greater.

Teradata RDBMS for UNIX SQL Reference

G-9
International and Japanese Character Support

User-Defined Character Set Restrictions

Figure G-1

Required EBCDIC Characters

0 1 2 3 4 5 6 7 8 9 A B C D E F
0 S P & - 0
1 / a j A J 1
2 b k s B K S 2
3 c l t C L T 3
4 d m u D M U 4
5 e n v E N V 5
6 f o w F O W 6
7 g p x G P X 7
8 h q y H Q Y 8
9 i r z I R Z 9
A
B $ , #
C < * % @
D ( ) '
E + > > =
F ~Ia ? Il

a. The logical not sign —I may also be shown as a caret (ë). ffadaqqi

G-10

Teradata RDBMS for UNIX SQL Reference
International and Japanese Character Support

User-Defined Character Sets: Alternative Currency Symbols

Introduction

European Alternative Currency Symbols

User-Defined Character Sets: Alternative Currency Symbols

If you want to use alternative currency symbols, ensure that the external character set translates to the internal set, and the internal-to-external code points match the internal hexadecimal values.

AltCurrency must be enabled in the RDBMS Control Record for characters other than the dollar sign ($), to be recognized as a currency symbol, and the internal values for alternate currency symbols depends upon whether the RDBMS is set up for International or Japanese character support.

For example, the external code for the dollar sign must map to 0x24, so that the dollar sign may be used as a currency symbol.

On a European feature site, the external symbol codes must be mapped to the Teradata RDBMS internal representation in a user-defined character set.

While it is recommended that the external to internal mappings preserve the semantics of a character exactly, in the case of alternate currency symbols, there may be occasions where this rule may not be possible to observe.

If a currency symbol that is required by applications, exists in the external character set, but there is no matching internal code, mapping this currency symbol to the internal general currency symbol should allow the application to function properly. Of course, other applications may interpret this character differently, with resulting confusion as to the nature of the currency symbol. Therefore, this practise should be avoided, if possible. The Teradata RDBMS treats such a character as if it were indeed the general currency symbol.

Teradata RDBMS for UNIX SQL Reference

G-11
International and Japanese Character Support

User-Defined Character Sets: Alternative Currency Symbols

Code choices on a European site are as follows:

European Symbols (International Hash) Description Internal Code (Hex) Decimal Value
$ Dollar sign 24 36
? Cent sign A2 162
? Pound sign A3 163
? Yen sign A5 165
general currency General currency symbol A8 168

Japanese Alternative Currency Symbols

Code choices on a Japanese site are as follows:

Japanese Symbols (Kanji Hash) Description Internal Code (Hex) Decimal Value
$ Dollar sign 24 36
? Yen sign 5C 92

The Japanese alternative currency symbols are mapped to the same internal code for KanjiEBCDIC, KanjiEUC, and KanjiShift-JIS. The yen sign can be used in exactly the same manner as the standard dollar sign ($).
Previous << 1 .. 209 210 211 212 213 214 < 215 > 216 217 218 219 220 221 .. 241 >> Next