[JBoss JIRA] Created: (TEIIDDES-967) 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
2:53 p.m.
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
3:06 p.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-967) 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
[
https://issues.jboss.org/browse/TEIIDDES-967?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIIDDES-967:
-----------------------------------------
Do you mean structure such as:
schema (some name)
\- tables
t1
t2
...
\- procedures
p1
p2
...
\- keys
k1
k2
...
\+ indexes
so that each of the relevant child types has it's own collapsible container?
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
3:14 p.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-967) 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
[
https://issues.jboss.org/browse/TEIIDDES-967?page=com.atlassian.jira.plug...
]
Van Halbert commented on TEIIDDES-967:
--------------------------------------
Yes, something like this would be nice.
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
7:11 a.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-967) 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
[
https://issues.jboss.org/browse/TEIIDDES-967?page=com.atlassian.jira.plug...
]
Barry LaFond commented on TEIIDDES-967:
---------------------------------------
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
7:13 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (TEIIDDES-967) 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
[
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
8:20 a.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-967) 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
[
https://issues.jboss.org/browse/TEIIDDES-967?page=com.atlassian.jira.plug...
]
Van Halbert commented on TEIIDDES-967:
--------------------------------------
In the tree hierarchy, its not about relationships as it is about organizational
presentation. Grouping of like object types makes it visually easier. I know, you
said a user can move them, but it should be visually easier out-of-the-box, not something
the user has to do.
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
8:22 a.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-967) 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
[
https://issues.jboss.org/browse/TEIIDDES-967?page=com.atlassian.jira.plug...
]
Van Halbert commented on TEIIDDES-967:
--------------------------------------
In the tree hierarchy, its not about relationships as it is about organizational
presentation. Grouping of like object types makes it visually easier. I know, you
said a user can move them, but it should be visually easier out-of-the-box, not something
the user has to do.
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
5436
days inactive
5437
days old
teiid-designer-issues@lists.jboss.org
6 comments
3 participants
participants (3)
-
Barry LaFond (JIRA) -
Steven Hawkins (JIRA)
-
Van Halbert (JIRA)