Subject | Transliteration problem in IBExpert |
---|---|
Author | Tim Gahnström |
Post date | 2005-05-18T09:20:10Z |
I have created a table with a charset ISO8859_1 (latin 1) to be able to be able to use some special european characters.
CREATE TABLE T_TEXTS (
STEXTID VARCHAR(15) NOT NULL,
SWEDISH VARCHAR(400) CHARACTER SET ISO8859_1 COLLATE SV_SV,
ENGLISH VARCHAR(400) CHARACTER SET ISO8859_1 COLLATE EN_US,
GERMAN VARCHAR(400) CHARACTER SET ISO8859_1 COLLATE DE_DE
);
It shouldn't be a big problem but I get an error when I try to add international characters such as åöäü from Ibexpert:
Error Message:
----------------------------------------
Arithmetic overflow or division by zero has occurred.
arithmetic exception, numeric overflow, or string truncation.
Cannot transliterate character between character sets.
--------------------------------------------------
It is strange because sometimes after I get this error I close the table and open it again then I see that the texts are actually in there. Also the special characters are there. So the issue seems to be with Ibexpert or something.
It works if I use UNICODE_FSS but I read I couldn't collate it. That might not be a big issue in this case but I am interfacing with other programs (mostly .NET) and ISO8859_1 seemed "more standard" then UNICODE_FSS so I figured I rather go with that. I would be happy to hear thoughts about the merits of either one of them.
Tim
CREATE TABLE T_TEXTS (
STEXTID VARCHAR(15) NOT NULL,
SWEDISH VARCHAR(400) CHARACTER SET ISO8859_1 COLLATE SV_SV,
ENGLISH VARCHAR(400) CHARACTER SET ISO8859_1 COLLATE EN_US,
GERMAN VARCHAR(400) CHARACTER SET ISO8859_1 COLLATE DE_DE
);
It shouldn't be a big problem but I get an error when I try to add international characters such as åöäü from Ibexpert:
Error Message:
----------------------------------------
Arithmetic overflow or division by zero has occurred.
arithmetic exception, numeric overflow, or string truncation.
Cannot transliterate character between character sets.
--------------------------------------------------
It is strange because sometimes after I get this error I close the table and open it again then I see that the texts are actually in there. Also the special characters are there. So the issue seems to be with Ibexpert or something.
It works if I use UNICODE_FSS but I read I couldn't collate it. That might not be a big issue in this case but I am interfacing with other programs (mostly .NET) and ISO8859_1 seemed "more standard" then UNICODE_FSS so I figured I rather go with that. I would be happy to hear thoughts about the merits of either one of them.
Tim