Dropping and recreating a table in the same txn disables PK [CORE104] #428
Comments
|
Commented by: Alice F. Bird (firebirds) Date: 2006-04-30 05:43 I have it fixed locally, to be committed some day the next week. |
Modified by: @dyemanovstatus: Closed [ 6 ] => Reopened [ 4 ] SF_ID: 1475979 => resolution: Fixed [ 1 ] => |
Modified by: @dyemanovstatus: Reopened [ 4 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 [ 10041 ] SF_ID: 1475979 => |
Modified by: Alice F. Bird (firebirds)description: SFID: 1475979# This problem was verified with both Fb 1.5 and 2.0 RC 1 Steps to reproduce the problem: 1) create a table with a primary key: create table test (acolumn int not null primary key); 2) disconnect & reconnect. 3) run the following script (with AUTO DDL OFF): drop table test; create table test (acolumn int not null primary key); commit; insert into test values (1); commit; It should fail, but it succeeds. Dropping and SET AUTODDL ON (or committing after the drop table => SFID: 1475979# This problem was verified with both Fb 1.5 and 2.0 RC 1 Steps to reproduce the problem: 1) create a table with a primary key: create table test (acolumn int not null primary key); 2) disconnect & reconnect. 3) run the following script (with AUTO DDL OFF): drop table test; create table test (acolumn int not null primary key); commit; insert into test values (1); commit; It should fail, but it succeeds. Dropping and SET AUTODDL ON (or committing after the drop table |
Modified by: @pcisarassignee: Dmitry Yemanov [ dimitr ] => |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
|
Commented by: @pcisar Fix confirmed for 2.1 Alpha 1. Test added. |
|
Commented by: @pcisar Reopened to update ticket information. |
Modified by: @pcisarFix Version: 2.1 Alpha 1 [ 10150 ] SF_ID: 1475979 => Fix Version: 2.1.0 [ 10041 ] => |
Modified by: @pcisarWorkflow: jira [ 10128 ] => Firebird [ 14328 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovQA Status: No test => Done successfully |
Submitted by: nandod (nandod)
Is related to QA53
SFID: 1475979#
Submitted By: nandod
This problem was verified with both Fb 1.5 and 2.0 RC 1
(SS, Win32, TCP/IP connection).
Steps to reproduce the problem:
1) create a table with a primary key:
create table test (acolumn int not null primary key);
2) disconnect & reconnect.
3) run the following script (with AUTO DDL OFF):
drop table test;
create table test (acolumn int not null primary key);
commit;
insert into test values (1);
insert into test values (1);
commit;
It should fail, but it succeeds. Dropping and
recreating the table in the same transaction did
something bad to the PK definition, which still appears
OK but the constraint isn't enforced.
SET AUTODDL ON (or committing after the drop table
statement) makes the problem go away.
The text was updated successfully, but these errors were encountered: