Book a Demo

Author Topic: BUG: visibilityKind problems with Data Model  (Read 2331 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
BUG: visibilityKind problems with Data Model
« on: December 13, 2006, 10:12:31 pm »
Database tables are classes stereotype as «table».  This causes specific rendering based on EA's data modelling profile.  One aspect of this specific rendering is that the visibilityKind indicator (public..private) on the columns is not rendered.

Database views are classes stereotyped as «view».  This should also remove the rendering of visibilityKind on the columns(if they are present - allowed since 800), but doesn't.

In addition, the visibilityKind is shown against the operations that indicate keys, foreign keys and triggers etc.  This doesn't seem right to me...

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

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: BUG: visibilityKind problems with Data Model
« Reply #1 on: December 14, 2006, 05:10:33 am »
Agreed. This looks like it was missed when «view» was added to the data modeling profile. As far as the operations go, it might always have been this way.

Perhaps you could loan some of your consistency to Sparx to help with this.
No, you can't have it!