Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different collation ID for altered computed column [CORE4934] #5225

Closed
firebird-automations opened this issue Sep 15, 2015 · 4 comments
Closed

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @cincuranet

* Prepare:

CREATE TABLE T_TRANSLATION_META (
F_TRM_ID BIGINT NOT NULL,
F_TRM_CODE VARCHAR(512) CHARACTER SET UTF8 NOT NULL COLLATE
UNICODE_CI
);
CREATE TABLE T_COUNTRY (
F_CNR_ID BIGINT NOT NULL,
F_TRM_NAME_ID BIGINT DEFAULT -1 NOT NULL,
CF_CNR_NAME COMPUTED BY (((select
F_TRM_CODE
from T_TRANSLATION_META
where F_TRM_ID = F_TRM_NAME_ID)))
);

`select rdb$collation_id from rdb$fields where rdb$field_name = 'RDB$5'` returns `null`.

ALTER TABLE T_COUNTRY ALTER CF_CNR_NAME COMPUTED BY (((select
F_TRM_CODE
from T_TRANSLATION_META
where F_TRM_ID = F_TRM_NAME_ID)));

And now the above query return `3`, although the computed column really didn't change.

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

v3 put the collation ID in rdb$fields.

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

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

resolution: Fixed [ 1 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: No test => Done successfully

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant