If you have a unique key that is the parent of a Foreign Key constraint, and you change the column name, on saving the column, EA helpfully asks: Column '<name>' is part of a foreign key relationship. Do you wish to propagate the change to connected tables?
Unfortunately, whether you answer Yes or No - nothing seems to happen!
[Edit] I've just noticed EA DOES make a change, it corrupts the key definition string on the link! That's not what I would call propagating to the connected tables...[/Edit]
EA may be behaving like Jim Trott in "The Vicar of Dibley": "No, no, no, Yes!"
Assuming that Sparx decide to fix this bug, there is the question of what does propagating mean?
For any useful naming convention the names of the column-sets at both ends of the foreign key constraint will either be identical or at least related. Therefore I suggest that if the old column name at the parent end is found anywhere in the corresponding column at the child end, then it should be replaced with the new column name.
Naturally, if I answered yes to the propagate question, EA should ask if I want to replace all or individually select.
Thoughts? Votes?
Paolo[size=0]©2007 Paolo Cantoni, -Semantica-[/size]