> How did you change this?

Well, I could reproduce the problem!

I use IBExpert personal edition v 2.00.5.
I think it's the tool's fault along with FB's fault.
IBExpert should drop the previous constraint or alter it, but instead it
adds another one with the same name.
The change was done with:

alter table "Operatii"
add constraint "FK_OperatiiDocument"
foreign key ("Document")
references "Documente"("Document")
on update CASCADE

The constraint was added previously with

alter table "Operatii"
add constraint "FK_OperatiiDocument"
foreign key ("Document")
references "Documente"("Document")


I wonder why FB allows adding a new constraint with the same name?


Adrian Roman