| Subject | Re: [ib-support] primary key not enforced after recreating the table |
|---|---|
| Author | Paul Reeves |
| Post date | 2002-12-06T07:40:24Z |
David Garamond wrote:
will be complete until you do. What you have discovered is that the
engine does some things immediately and defers others until commit.
Is this a bug or is it 'as-designed' (or both)? I don't know without
investigating things further. However, the usual practice with DDL
statements is to commit after each one is executed.
Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase
> yes, that _is_ my problem. why doesn't it fail after the table isYou might try committing after the drop and the create. Neither action
> dropped and recreated??? i am deliberately inserting the value "1" so
> the second insert would be rejected by the unique index. but after
> DROP+CREATE, i can insert duplicate rows.
will be complete until you do. What you have discovered is that the
engine does some things immediately and defers others until commit.
Is this a bug or is it 'as-designed' (or both)? I don't know without
investigating things further. However, the usual practice with DDL
statements is to commit after each one is executed.
Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase