Book a Demo

Author Topic: BUG: Parent key change NOT propagated  (Read 2467 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8617
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
BUG: Parent key change NOT propagated
« on: March 14, 2007, 11:14:29 pm »
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]
« Last Edit: March 14, 2007, 11:21:10 pm by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

alicecbrown

  • EA User
  • **
  • Posts: 30
  • Karma: +0/-0
  • Silence condones.
    • View Profile
Re: BUG: Parent key change NOT propagated
« Reply #1 on: March 15, 2007, 05:07:53 am »
Yes, ask the question, and take us through the path, if we say 'yes, to each individual case'.
AND, further, do as the CADRE's TEAMWORK wonderful family of tools did, before it was bought out and buried :'(: Bring up little windows when we change one thing (upon request) to show the effect it will propagate, if all was right with the world (and EA).  TEAMWORK highlighted the effects on Design, Code and Test Plans.
McCabe's Family of tools will show you the change in paths, when you run one of their Complexity diagnostic tools.  Move up into the Big Time.  Show us what our actions have wrought. ;)
An humble acolyte in the fields of learning
Unto him who is given much, much is required.

jeshaw2

  • EA User
  • **
  • Posts: 701
  • Karma: +0/-0
  • I'm a Singleton, what pattern are you?
    • View Profile
Re: BUG: Parent key change NOT propagated
« Reply #2 on: March 15, 2007, 08:42:56 am »
You got my vote.  Provide both options:  Ask for each or All.
Verbal Use Cases aren't worth the paper they are written upon.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8617
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: BUG: Parent key change NOT propagated
« Reply #3 on: March 15, 2007, 11:05:07 pm »
Sparx have confirmed they will address the bug ("We have added your suggestion to our feature request list."  ???).  But they haven't mentioned what the fix will look like.   :-X

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!