History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEADEV-31534
Type: Usability Problem Usability Problem
Status: Open Open
Priority: Normal Normal
Assignee: Gregory Shrago
Reporter: Taras Tielkes
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
IDEA: Development

ER diagram cluttered when using @MappedSuperClass

Created: 18 Jul 08 01:14   Updated: 21 Oct 08 17:38
Component/s: J2EE.EJB3, J2EE.Hibernate
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

Build: 8,587
Severity: High


 Description  « Hide
Many projects define some abstract base class for all entities.
Often this base class has at least "id" and "version" persistent attributes defined, and contains @MappedSuperClass annotation.

When most/all of the entities derive from such a mapped super class, the ER diagram gets cluttered quickly, because of all the derived->base edges.
It would be very convenient if there was a toggle button to "materialize" properties from a @MappedSuperClass to the derived classes (in the ER diagram, not in code of course).

So, in above example...when the toggle was enabled, the "id" and "version" properties would simply be listed on all the nodes of the derived classes, and the "red" arrows linking derived->base classes would no longer be drawn. Perhaps the "property" icon for such "materialized" properties from a @MappedSuperClass could get an icon decoration: a red "up" arrow on top of the green round "p" icon.



 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.