Records left in RDB$PAGES after rollback of CREATE TABLE statement [CORE2284] #2710
Assignees
Comments
|
Commented by: @hvlad The reason is that records in RDB$PAGES stored by system transaction and not rolled back with user transaction. |
|
Commented by: @romansimakov It duplicates CORE5677 but this test case is more simple and can be used for automated test for QA. |
Modified by: @romansimakovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Duplicate [ 3 ] Fix Version: 3.0.3 [ 10810 ] Fix Version: 4.0 Beta 1 [ 10750 ] assignee: Roman Simakov [ roman-simakov ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
-cannot create index RDB$PRIMARY12
SQL>
SQL> rollback;
SQL>
SQL> select count(*) from rdb$pages where rdb$relation_id >=
CON> (select rdb$relation_id from rdb$database);
============
4
Commits: 9afef19 bfb008f
The text was updated successfully, but these errors were encountered: