You are right! I just checked. Indeed the constraint is dropped and after
that the new one is added.
Both operations are done in a single transaction.
In this case, the message given is:

"Unsuccessful execution caused by system error that does not preclude
successful execution of subsequent statements.
index unexpectedly deleted."

Whatever that means...


Interesting, if I drop the constraint in a separate transaction, and after
that I add a the constraint again with cascade, it works...

It seems a FB problem indeed.


Adrian Roman

----- Original Message -----
From: "Ales Kahanek" <ales.kahanek@...>
To: <ib-support@yahoogroups.com>
Sent: Monday, July 29, 2002 5:26 PM
Subject: RE: [ib-support] Index unexpectedly deleted?


> Hi Adrian,
> I use use IBExpert as well but I do not think it is caused by IBExpert. If
> you looked properly, you would see, that IBExpert issued 2 commands -
"drop
> constraint" and "create constraint". Example from my db:
> ?
> ALTER TABLE CASH_OUT_ITEMS DROP CONSTRAINT FK_CASH_OUT_ITEMS__CASH_OUT;
>
> alter table CASH_OUT_ITEMS
> add constraint FK_CASH_OUT_ITEMS__CASH_OUT
> foreign key (CSO_ID)
> references CASH_OUT(CSO_ID)
> on delete CASCADE;
>
> This should be problem with Firebird, I guess.
> Ales
>