| Character set for 10g database for Japanese Language [message #182642] |
Mon, 17 July 2006 08:00  |
himang
Messages: 282
Registered: March 2005
Location: Bangalore
|
Senior Member |
|
|
We have 10g Enterprise Edition Release 10.1.0.5.0 database in which the Character set settings are
NLS_CHARACTERSET - AL32UTF8
NLS_NCHAR_CHARACTERSET - AL16UTF16
We are going to support Japanese language (Kanji as well as Kana characters) in our application. The application shall send the data in form of XML string (UTF-16 characterset).
Currently our fields are defined in terms of VARCHAR2 and not NVARCHAR2 (as it is an existing application). Wanted to know whether we can have problem storing and retrieving Kanji characters with current setup.
Please let me know if I need to provide some more info…
Regards
Himanshu
[Updated on: Mon, 17 July 2006 08:00] Report message to a moderator |
|
|
|
|
|
| Re: Character set for 10g database for Japanese Language [message #183562 is a reply to message #182642] |
Fri, 21 July 2006 06:29  |
gjhyland
Messages: 1
Registered: July 2006
Location: Australia
|
Junior Member |
|
|
Because you are using a multi-byte characterset you wont be able to store as many characters in columns of tables defined as VARCHAR2(n) because n bytes are available for storage. As I am sure you know - UTF8 is variable number of bytes per character, each character consuming as many as 3 bytes of storage (the ASCII range using one byte). UTF16 is a double byte characterset.
So for VARCHAR2(1000), you could get as few as 1000/3 characters loaded with UTF8 but with UTF16 you will only be able to load 1000/2 characters.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
