-
Omnis Studio with DB2 and unicode
Hi,
Is there anyone out there that uses any Unicode Version of Omnis Studio with DB2 and a UTF8 database?
I am having problems with the saving of Unicode data in DB2 using bind variables with numerous versions of Omnis Studio since 4.3.2.1, where saving data with bind variables does not save the data in DB2 correctly, using explicit SQL however does save the data correctly, and I would just like to know if anyone has actually gotten this to work reliably in any version of Omnis Studio.
The unicode character I am trying to save is ‘ń’. The correct unicode representation of this value is xC5 xBA. When using bind variables Omnis stores this as xC4 xB9 xE2 x80 x9E in the database.
UPDATE TEST SET TESTCOL = @[MyVar] <- this stores incorrect data on the database
UPDATE TEST SET TESTCOL= ‘ń’ <- this stores the data in the DB2 table correctly
SELECT TESTCOL FROM TESTTABLE <- this fetches the incorrectly stored data and displays the bad unicode unicode database string in Omnis correctly, but the correctly stored data in the database is not fetched correctly
If this really is a bug, I really cannot believe no one has seen this in the past 12 years. Perhaps we are the only ones out there using DB2, or we are doing something wrong. It would help to know that someone is actually not having problems.
Regards
Rudolf Bargholz
Log in to reply.