[
https://issues.jboss.org/browse/TEIIDDES-967?page=com.atlassian.jira.plug...
]
Barry LaFond edited comment on TEIIDDES-967 at 5/24/11 8:11 AM:
----------------------------------------------------------------
Not sure what you mean by "folder".
Teiid Designer's Relational metamodel basically reflects the structural/parent-child
containment. PK/FK/UC objects/references, however, are defined as "references"
but sort of inferred and displayed as "containment". Visually we could put them
in another container (i.e. folder). The Tree structure would be easy to tweak using our
content/label providers. However, would the ER/Package Diagram really change?
was (Author: blafond):
Not sure what you mean by "folder".
Teiid Designer's Relational metamodel is basically reflects the
structural/parent-child containment. PK/FK/UC objects/references, however, are defined as
"references" but sort of inferred and displayed as "containment".
Visually we could put them in another container (i.e. folder). The Tree structure would be
easy to tweak using our content/label providers. However, would the ER/Package Diagram
really change?
Usability: Indexes/Keys should be placed into their own folder,
because they just add to unnecessary scolling when they are not used for data access
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-967
URL:
https://issues.jboss.org/browse/TEIIDDES-967
Project: Teiid Designer
Issue Type: Enhancement
Components: Modeling
Affects Versions: 7.1.1
Reporter: Van Halbert
When keys/indexes are listed, they get in the way of viewing. They should be placed
into their own folder.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira