Display less columns in table/diagram

[Bill Egge]

I have a diagram with tables in it and a few tables have over 200 columns.  It takes a lot of diagram space for these tables and I would like to reduce this space by eliminating the display of non important columns.

Is this possible?  Any hacky tricks to accomplish it?

:-/

[Paolo F Cantoni]

I have a diagram with tables in it and a few tables have over 200 columns.  It takes a lot of diagram space for these tables and I would like to reduce this space by eliminating the display of non important columns.

Is this possible?  Any hacky tricks to accomplish it?

 :-/

Hi Bill,
You can add "display control" stereotypes to your model (I preface mine with tilde "~" so they stand out).  By applying these to the columns you DON'T want displayed, you can control their visibility via the Set Feature Visibility (Ctrl-Shift-Y).  It's the box in the bottom left corner...  (Hide Stereotyped Features)

HTH,
Paolo

[Eve]

I suspect that there isn't actually any way of doing it.  At least not without compromising any DDL generation from the table.

My reasoning is that the columns already are stereotyped.  You can change this stereotype to hide some, but that will (I think) break the generation.

Possibly the best way to do it is to make a copy of your table and delete the irrelevant columns from the copy.

Simon

[Paolo F Cantoni]

[size=13][SNIP][/size]
My reasoning is that the columns already are stereotyped.  You can change this stereotype to hide some, but that will (I think) break the generation.
[size=13][SNIP][/size]

Sorry Bill,
I forgot EA DOESN'T implement UML2 here and only allows one stereotype per attribute...

Orthogonality, Orthogonality, Orthogonality! ^TM

Regretfully,
Paolo

BTW: I've previously suggested to Sparx that they provide the same functionality for tagged values - which would be more useful.

[thomaskilian]

I suspect that there isn't actually any way of doing it.  At least not without compromising any DDL generation from the table.

My reasoning is that the columns already are stereotyped.  You can change this stereotype to hide some, but that will (I think) break the generation.

Possibly the best way to do it is to make a copy of your table and delete the irrelevant columns from the copy.

Simon

... or you're doing like Bruce: create a specialized class stereotyped as <<facade>> and add only the methods/attributes of interest.