|
-
Nclobs
Can NCLOBs be used in a database where the character set is defined as WE8ISO8859P1 to hold UNICODE data?
Oracle it's not just a database it's a lifestyle!
--------------
BTW....You need to get a girlfriend who's last name isn't .jpg
-
Oracle it's not just a database it's a lifestyle!
--------------
BTW....You need to get a girlfriend who's last name isn't .jpg
-
If I understand this correctly, NCLOB wants to store it's characters in double byte format (AL16UTF16). WE8ISO8859P1 (Western Europeeen)is a single byte character set. UTF8 is also a single byte character set.
I may be all washed up on this one and would appreciate any/all corrections to my statements..
-
Hmmm, I was under the impression that UTF8 was kind of a "catch all" charater set.
Oracle it's not just a database it's a lifestyle!
--------------
BTW....You need to get a girlfriend who's last name isn't .jpg
-
You're right.
UTF8 will store up to 4 byte characters and I believe all the Unicode Character Set Version 2.something (UCS-2).
Here's the answer to your original question... It's in chapter 5 of the "Oracle9i Database Globalization Support Guide":
Documents in NCLOB are stored as UTF-16 regardless of the database character set or national character set. The storage space requirement is the same as for CLOBs. Document contents are converted to UTF-16 when they are inserted into a NCLOB column. If you want to store multilingual documents in a non-Unicode database, then choose NCLOB. However, content search on NCLOB is not yet supported.
PS. Looks like this applies to 8.1.x too.
Last edited by KenEwald; 11-19-2003 at 01:54 AM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote