From: Adriano d. S. F. (JIRA) <tr...@fi...> - 2010-06-18 12:39:11
|
Problems may happen when issuing DDL commands in the same transaction after issue CREATE COLLATION -------------------------------------------------------------------------------------------------- Key: CORE-3056 URL: http://tracker.firebirdsql.org/browse/CORE-3056 Project: Firebird Core Issue Type: Bug Components: Charsets/Collation, Engine Affects Versions: 2.5 RC2, 2.5 RC1, 3.0 Initial, 2.1.3, 2.5 Beta 2, 2.5 Beta 1, 2.1.2, 2.0.5, 2.1.1, 2.5 Alpha 1, 2.0.4, 2.1.0, 2.0.3, 2.0.2, 2.0.1, 2.0.0 Reporter: Adriano dos Santos Fernandes Test case adapted from Vlad's comment in CORE-2826: --------------- CREATE COLLATION UNICODE_NOPAD FOR UTF8 FROM UNICODE NO PAD; --COMMIT; -- (1) RECREATE TABLE tst1_nopad ( k1 VARCHAR(3) COLLATE UNICODE_NOPAD, k2 INT, k3 CHAR(1) COLLATE UNICODE_NOPAD, PRIMARY KEY (k1, k2, k3) ); COMMIT; SHOW TABLE tst1_nopad; --------------- Note, without COMMIT at point (1), fields of tst1_nopad will have collate UTF8! Also, multiple CREATE COLLATION for the same charset raises unique violation error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |