You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason of BUGCHECK is that on second commit new relation_id is assigned to both newly created tables and when foreign key's index created master relation can't be found in metadata cache.
Patch below solve this issue but i can't say about side effects so far.
Submitted by: @hvlad
SQL> set autoddl off;
SQL> create table test_cs__master
CON> (
CON> str_pk varchar(32) character set UNICODE_FSS not null,
CON>
CON> primary key (str_pk)
CON> );
CON>
SQL> create table test_cs__detail
CON> (
CON> str_pk varchar(32) character set WIN1251 not null,
CON>
CON> foreign key (str_pk) references test_cs__master (str_pk)
CON> );
SQL>
SQL> commit;
Statement failed, SQLSTATE = 42000
unsuccessful metadata update
-partner index segment no 1 has incompatible data type
SQL> commit;
Statement failed, SQLSTATE = 08006
connection lost to database
SQL>
Firebird.log contains record :
internal Firebird consistency check (partner index description not found (175), file: idx.cpp line: 191)
The text was updated successfully, but these errors were encountered: