OK, I've managed to delete the "ghost" FKs by creating new associations and defining new FK relationships and then deleting them. But here is an interesting "feature":
1. I create (directed) association
2. I add FK relationship on it
3. I delete FK relationship by opening foreign key dialog box and deleting it from there.
4. EA leaves the association ofcourse, but it also leaves association roles and multiplicities it added when creating the FK relationship
5. I've checked, there are no FK operations left
6. on the same association, I try to add a new FK relationship using the FK dialog box: when I select appropriate columns in both tables and hit the SAVE button - IT DOESN'T HAPPEN: no FK relationship is added, and EA doesn't report any error or warning.
although the mentioned association should have been left "clean" from the previous deletion of FK relationship - it obviously has something that creates this problem. You have to delete the association as well and then start all over again.
-----------------------------but never mind that, it's a feature I can live with, but this IS a problem: ----------------
I'm using build 827 of EA, I'm modeling MS SQL server database
- Let's say you have tables A and B
- there are 2 FK relationships you have to add from A to B
- first I add association 1 from A to B
- then I add a FK from column A1 to column B1; EA gives name to this FK constraint FK_A_B, and it also gives a name to association role of table A: +FK_A_B
- then I add second association 2 from A to B
- then I TRY to add a FK on that assoc.2. from columns A2 to column B1; EA has tried to give name to this FK constraint FK_A_B, but since such constraint already exists it gives warning.
- just for any case I try to save one more time but it gives the same warning
- OK, I rename manually the name of the FK constraint to "FK_A_B1"
- then I press the save button
- EA then makes a MESS:
-- it gives a name to association role of table A: +FK_A_B11 (notice two "1")
-- when you open FK constraint dialog box, there the name of the seconf FK constraint is also FK_A_B11 (EA added second "1" I guess)
-- watching the FK constraint in the dialog box, it is, well, broken: target column B1 is left as it is, but the source column A2 is missing!
-- watching the first FK constraint in the dialog box, I notice the first constraint is broken in the same way!
-- then when you open operations dialog box of the table A, you'll find two identically named operations: FK_A_B1 (notice just one "1")
- if you add other associations and FK constraints between A and B, the problem just multiplies
This is quite serious. I can't find anything that would indicate that I have messed things up.
Any suggestions?
