Subject | Re: [ib-support] primary key not enforced after recreating the table |
---|---|
Author | David Garamond |
Post date | 2002-12-06T05:26:14Z |
Louis Kleiman wrote:
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.
i can always reproduce this problem. sorry, haven't tried 1.5 or windows
at the moment.
--
dave
> I don’t know PHP, but it looks like the following statement should failit's python, not php :)
> on the second execution:
> cur.execute("INSERT INTO T1 VALUES (?,?)", (1,''))yes, that _is_ my problem. why doesn't it fail after the table is
>
> because you are trying to insert the same record every time with the
> values 1 and ‘’.
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.
i can always reproduce this problem. sorry, haven't tried 1.5 or windows
at the moment.
--
dave