FB3 - crash (consistency check) when creating view on table which has column with character set none, database default charset is utf8, and utf8 default collation is 'unicode'. [CORE5448] #5719
Comments
Modified by: Zoran Vučenović (zoran.vucenovic)description: Please do the following for steps in FB 3.0.1: /* 1. Create new database and set utf8 to be the default char set (change db path to whatever you want, in my example "test1" is an alias defined in database.conf) */ /* 2. set default collation of utf8 to be unicode */ /* 3. create table with a field which has character set none */ /* 4. Now, try to create view which reads this field */ After this, you get: Statement failed, SQLSTATE = XX000 And database seems to be corrupted afterwards. There is no such problem with FB 2.5. I am prepairing to migrate my databases to FB 3, but because of this bug, I'm still remaining on 2.5.6. => Please do the following four steps in FB 3.0.1: /* 1. Create new database and set utf8 to be the default char set (change db path to whatever you want, in my example "test1" is an alias defined in database.conf) */ /* 2. set default collation of utf8 to be unicode */ /* 3. create table with a field which has character set none */ /* 4. Now, try to create view which reads this field */ After this, you get: Statement failed, SQLSTATE = XX000 And database seems to be corrupted afterwards. There is no such problem with FB 2.5. I am prepairing to migrate my databases to FB 3, but because of this bug, I'm still remaining on 2.5.6. |
|
Commented by: Zoran Vučenović (zoran.vucenovic) I'm attaching the screenshot. |
Modified by: Zoran Vučenović (zoran.vucenovic)Attachment: isql-screenshot.png [ 13053 ] |
|
Commented by: @pavel-zotov Confirmed on WI-T4.0.0.494\ SQL> create database 'localhost:C:\FBTESTING\qa\fbt-repo\tmp\c5448.fdb' default character set utf8; |
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
|
Commented by: @hvlad The bugcheck reason is fixed (thus i consider this ticket as fixed) but there is another problem: SQL> create view view1 |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0.2 [ 10785 ] Fix Version: 4.0 Alpha 1 [ 10731 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Deferred Test Details: see here issue 07.02.2017 0915 |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] Test Details: see here issue 07.02.2017 0915 => see here issue 02.02.2017 by Vlad |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Deferred => Covered by another test(s) Test Details: see here issue 02.02.2017 by Vlad => See test for CORE5846 (it was made on this ticket basis). |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Zoran Vučenović (zoran.vucenovic)
Attachments:
isql-screenshot.png
Please do the following four steps in FB 3.0.1:
/* 1. Create new database and set utf8 to be the default char set (change db path to whatever you want, in my example "test1" is an alias defined in database.conf) */
create database 'inet://localhost/test1' default character set utf8;
/* 2. set default collation of utf8 to be unicode */
alter character set utf8 set default collation unicode;
/* 3. create table with a field which has character set none */
create table table1
(
fld1 char(1) character set none
);
/* 4. Now, try to create view which reads this field */
create view view1
as
select fld1 from table1
;
After this, you get:
Statement failed, SQLSTATE = XX000
internal Firebird consistency check (pointer page lost from DPM_delete_relation (246), file: dpm.cpp line: 1159)
And database seems to be corrupted afterwards.
There is no such problem with FB 2.5. I am prepairing to migrate my databases to FB 3, but because of this bug, I'm still remaining on 2.5.6.
Commits: 1a075b8 a5f73c5
====== Test Details ======
See test for CORE5846 (it was made on this ticket basis).
The text was updated successfully, but these errors were encountered: