Book a Demo

Author Topic: Propagating column (attribute) changes  (Read 3415 times)

dbax

  • EA User
  • **
  • Posts: 69
  • Karma: +0/-0
  • One EA To Rule Them All
    • View Profile
Propagating column (attribute) changes
« on: July 11, 2008, 01:21:12 pm »
Hi,

I have a data model with quite a few tables (classes) and of course relationships between them. This model has been reverse-engineered from an existing SQL Server schema. As I am documenting table and column definition I am expecting that changes to columns participating in any constraints, say foreign key constraints in this example, are cascaded (propagated) to all tables where this particular column is used. However, those changes are not applied to other tables where the column is also used - even though EA properly identifies that the column is used elsewhere and prompts to propagate changes.
More specifically I am expecting that following properties of a foreign key column will be cascaded (of course EA should still prompt whether to do so - this is a correct behaviour):
1. Notes - I use this property to document column definition and this is essential for documentation purpose as my organization is using EA as repository of information.
2. Column Name - this is a mandatory behaviour for me for logical data modeling (PIM).

I hope this can be addressed in the next build. At the same time, if there is something at the settings level within EA that can resolve this, and that I am missing, I would appreciate someone's guidance.
Regards,

DBax