Issue Details (XML | Word | Printable)

Key: CORE-3056
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Adriano dos Santos Fernandes
Reporter: Adriano dos Santos Fernandes
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Problems may happen when issuing DDL commands in the same transaction after CREATE COLLATION was issued

Created: 18/Jun/10 12:34 PM   Updated: 23/Sep/15 12:58 PM
Component/s: Charsets/Collation, Engine
Affects Version/s: 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.1.0, 2.0.4, 2.5 Alpha 1, 2.1.1, 2.0.5, 2.1.2, 2.5 Beta 1, 2.5 Beta 2, 2.1.3, 3.0 Initial, 2.5 RC1, 2.5 RC2
Fix Version/s: 3.0 Alpha 1

Issue Links:
Relate

QA Status: Done with caveats
Test Details:
1. Results are identical on: LI-T3.0.0.31827 (64 bit) and WI-T3.0.0.31827 (32 bit).
2. Despite of ticket issue that it was fixed only in 3.0, following script works OK on also on 2.5
   (tested on WI-V2.5.5.26861; differences are only in stderr).
3. ## TODO ###
   Uncomment lines "--,constraint test_pk1 primary key" after CORE-4783 will be fixed, and add
   statement 'alter table drop constraint <PK>" before each DROP TABLE statements.


 Description  « Hide
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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Pavel Cisar added a comment - 23/Sep/15 12:58 PM
Test created.