"Carlos" <miotromailcarlos@[EMAIL PROTECTED]
> schrieb im Newsbeitrag
news:c03f11e2-8cd4-41ff-bba6-b0a0f6c3c7e7@[EMAIL PROTECTED]
Apr 15, 3:04 pm, "André Hartmann" <andrehartm...@[EMAIL PROTECTED]
>
wrote:
>I cannot see the point of storing UNICODE (UTF8? UTF16?) in a
>WE8MSWIN1252 database... (you don't specify the NLSup****t codepage for
>NVARCHARS/NCHARS)
>
>The DB codepage should be unicode (AL32UTF8).
>
Hi, if that is so (unicode cannot be stored into databases that do not
have a unicode character set) then why can I create tables with unicode
columns (NCHAR, NVARCHAR2, NCLOB) in such databases? Wouldnt it be more
appropriate then for Oracle to cast errors when trying so? To say it the
other way round, the sheer fact that it is possible to declare unicode
columns in the database implied to me that it is possible to store such
values. Am I wrong here?
André
:)
|
