Re: Migration from sqlserver to oracle 8i: character set conversionproblems
Date: Tue, 18 Feb 2003 22:38:14 +0100
Message-ID: <jk955vohv6r812iih3vrpf4el4kvk7rrnl_at_4ax.com>
On Tue, 18 Feb 2003 16:09:34 +0100, Irmen de Jong <irmen_at_-NOSPAM-REMOVETHIS-xs4all.nl> wrote:
>DA Morgan wrote:
>
>> This has nothing to do with column types, VARCHAR2 or NVARCHAR. It has
>> to do with the character set of the database.
>
>The database config itself is ok, because I can store and retrieve
>unicode characters just fine by using a test Java program that
>accesses the oracle destination database directly trough the JDBC
>driver. Storing € and retrieving it works perfectly (I checked the
>character code that is returned, this is 0x20ac, and that is
>the unicode code for the € symbol).
>
>So I don't think it is a database character set issue.
>
>Irmen de Jong
Fact 1: The € is NOT an unicode character
Fact 2: The € does NOT belong to the WE8ISO8859P1 character set, as
the ISO couldn't agree about the location of the € in the character
set.
Fact 3: This is why the WE8ISO8859P15 character set was invented
Fact 4: OF COURSE Microsux didn't want to follow this and invented the
MSWIN1252 character set.
In summary: You DON'T need Unicode, and the issue you are having DEFINITELY IS a CHARACTER SET ISSUE.
[Quoted] [Quoted] Next time, if you already think you know better, please DON'T POST and see for yourself
Regards
Sybrand Bakker, Senior Oracle DBA
To reply remove -verwijderdit from my e-mail address Received on Tue Feb 18 2003 - 22:38:14 CET