Alter table not respecting collation [CORE2426]

[firebird-automations]

Submitted by: @WarmBooter

Is related to QA398

Table already exists with FIELD_A VARCHAR(14) CHARSET WIN1252 COLLATE WIN1252;

Create a domain A_DOMAIN VARCHAR(14) CHARSET WIN1252 COLLATE WINPT_BR;

Use "alter table" to change FIELD_A to type A_DOMAIN

Try to create a FK in some other table, referencing FIELD_A and you will get:

This operation is not defined for system tables.
unsuccessful metadata update.
partner index segment no 1 has incompatible data type.

Looks like FIELD_A still has old collation. If I change system tables to force the new collation, I can create the FK.

Commits: 34bf21b

[firebird-automations]

Commented by: @asfernandes

More dangerous behavior observed:

create domain A_DOMAIN VARCHAR(14) CHARacter SET WIN1252 COLLATE WINPT_BR;
create domain B_DOMAIN VARCHAR(14) CHARacter SET ISO8859_1 COLLATE PT_BR;

create table t (FIELD_A VARCHAR(14) CHARacter SET WIN1252 COLLATE WIN1252);
alter table t alter field_a type b_domain;

show table t; -- colattion changes to de_de

[firebird-automations]

Modified by: @asfernandes

Version: 2.5 Beta 1 [ 10251 ]

assignee: Adriano dos Santos Fernandes [ asfernandes ]

[firebird-automations]

Modified by: @asfernandes

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

resolution: Fixed [ 1 ]

Fix Version: 2.5 RC1 [ 10300 ]

[firebird-automations]

Modified by: @pcisar

Link: This issue is related to QA398 [ QA398 ]

[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