Collation not propagated between record formats [CORE1432]

[firebird-automations]

Submitted by: prenosil (prenosil)

Relate to CORE3045
Is related to QA331

Votes: 2

* First create table/column with domain using case sensitive collation and insert some data:

CREATE DOMAIN D_1250 VARCHAR(10) CHARACTER SET WIN1250 COLLATE WIN1250;

CREATE TABLE T (I INTEGER, A D_1250);
INSERT INTO T VALUES(10, 'a');
COMMIT;

SELECT * FROM T WHERE A='A';
Records affected: 0

So far o.k.

* And now alter the column to use domain with case insensitive collation:
CREATE DOMAIN D_CZ VARCHAR(10) CHARACTER SET WIN1250 COLLATE WIN_CZ;
ALTER TABLE T ALTER A TYPE D_CZ;

But as you can see here, the new collation is not used:
SELECT * FROM T WHERE A='A';
Records affected: 0

Although there are now two record formats in RDB$FORMATS,
the engine use values from the old one (because this format is used to store our data)
and does not convert data to new format.

Here, simple dummy update will "fix" it:
UPDATE T SET I=I;

SELECT * FROM T WHERE A='A';
I A
=========== ==========
10 a
Records affected: 1

Commits: cf7ae27

[firebird-automations]

Modified by: @asfernandes

assignee: Adriano dos Santos Fernandes [ asfernandes ]

[firebird-automations]

Modified by: @pcisar

Workflow: jira [ 12911 ] => Firebird [ 15045 ]

[firebird-automations]

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 Beta 1 [ 10251 ]

[firebird-automations]

Modified by: @dyemanov

Link: This issue relate to CORE3045 [ CORE3045 ]

[firebird-automations]

Modified by: @pcisar

Link: This issue is related to QA331 [ QA331 ]

[firebird-automations]

Commented by: @pcisar

QA test added.

[firebird-automations]

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

[firebird-automations]

Modified by: @pavel-zotov

QA Status: No test

[firebird-automations]

Modified by: @pavel-zotov

QA Status: No test => Done successfully