Subject | Re: problem solved...in part |
---|---|
Author | Roman Rokytskyy |
Post date | 2007-11-08T22:17:05Z |
Helen,
in the data.
bug report) - you get this error when you drop the foreign key, then
table, then create the same table, fill data and, finally, restore the
foreign key (commit after each operation). I had this issue in my
benchmark code where I had to clean a table. It had been fixed in FB 2.0.
Roman
> I think possibly the original problem arose because you didn'tcommit the transaction that performed the DDL before starting to pump
in the data.
>I had a reproducable test case (and if I'm not mistaken, had created a
> internal gds software consistency check (partner index description
> not found (175))
bug report) - you get this error when you drop the foreign key, then
table, then create the same table, fill data and, finally, restore the
foreign key (commit after each operation). I had this issue in my
benchmark code where I had to clean a table. It had been fixed in FB 2.0.
Roman