You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
C:\Programme\Firebird\Firebird_2_5 :: bin\isql -u milu -p moin eins25
Database: eins25, User: milu
SQL> set names cp1252;
SQL> set warnings on;
SQL> create table tascii (s varchar(10) character set ascii);
SQL> create table tlatin (s varchar(10) character set latin1);
SQL> insert into tascii values ('Käse');
SQL> select * from tascii;
S
Käse
SQL> -- This should have raised an error, or truncation warning.
SQL> insert into tlatin values ('Käse');
SQL> select * from tlatin;
S
Käse
SQL> insert into tlatin select * from tascii;
Statement failed, SQLSTATE = 22018
arithmetic exception, numeric overflow, or string truncation
-Cannot transliterate character between character sets
SQL> -- This is wrong, all ASCII should go into a Latin1 table.
SQL> -- Probably a consequence of the ASCII insertion bug above.
SQL> commit;
SQL> drop table tascii;
SQL> drop table tlatin;
SQL> quit;
Submitted by: Michael Ludwig (milu)
Is related to QA562
Here's a script to insert "Käse" into a column of CHARACTER SET ASCII.
This shouldn't be possible. I think it is a bug.
C:\Programme\Firebird\Firebird_2_5 :: chcp 1252
Aktive Codepage: 1252.
C:\Programme\Firebird\Firebird_2_5 :: bin\isql -u milu -p moin eins25
Database: eins25, User: milu
SQL> set names cp1252;
SQL> set warnings on;
SQL> create table tascii (s varchar(10) character set ascii);
SQL> create table tlatin (s varchar(10) character set latin1);
SQL> insert into tascii values ('Käse');
SQL> select * from tascii;
S
Käse
SQL> -- This should have raised an error, or truncation warning.
SQL> insert into tlatin values ('Käse');
SQL> select * from tlatin;
S
Käse
SQL> insert into tlatin select * from tascii;
Statement failed, SQLSTATE = 22018
arithmetic exception, numeric overflow, or string truncation
-Cannot transliterate character between character sets
SQL> -- This is wrong, all ASCII should go into a Latin1 table.
SQL> -- Probably a consequence of the ASCII insertion bug above.
SQL> commit;
SQL> drop table tascii;
SQL> drop table tlatin;
SQL> quit;
This originated here:
Inserting Käse into a CHARACTER SET ASCII column
http://tech.groups.yahoo.com/group/firebird-support/message/112680 (archive)
Commits: 64b3a55
====== Test Details ======
2.5.0 also raises error despite ticket's issue "Affects Version/s: 2.5.0"
The text was updated successfully, but these errors were encountered: