[JBoss JIRA] (TEIIDDES-382) Clicking on almost any model property results in incorrect description being displayed
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-382?page=com.atlassian.jira.plug... ]
Barry LaFond commented on TEIIDDES-382:
---------------------------------------
Clicking on properties to view the "status line/description" is a very minor use case and the work-around is to mouse-over to see the tooltip.
With our plans to re-invent the user experience in Komodo, pushing this to NO FUTURE bucket for now
> Clicking on almost any model property results in incorrect description being displayed
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-382
> URL: https://issues.jboss.org/browse/TEIIDDES-382
> Project: Teiid Designer
> Issue Type: Bug
> Components: Views
> Affects Versions: 7.4
> Reporter: Michael Walker
> Assignee: Dan Florian
> Priority: Minor
> Fix For: No Future
>
>
> Click on a property of a column. Below, you will see:
> i. NameInSource of Entity
> This is likely to be the description of the "NameInSource" property. We incorrectly assign the same description to every other property. This is not helpful.
> Each property should have an accurate description that informs the user what the property represents. They should not have to do to the PDF documentation every time to look this information up - it's too tedious.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (TEIIDDES-382) Clicking on almost any model property results in incorrect description being displayed
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-382?page=com.atlassian.jira.plug... ]
Barry LaFond updated TEIIDDES-382:
----------------------------------
Assignee: (was: Dan Florian)
> Clicking on almost any model property results in incorrect description being displayed
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-382
> URL: https://issues.jboss.org/browse/TEIIDDES-382
> Project: Teiid Designer
> Issue Type: Bug
> Components: Views
> Affects Versions: 7.4
> Reporter: Michael Walker
> Priority: Minor
> Fix For: No Future
>
>
> Click on a property of a column. Below, you will see:
> i. NameInSource of Entity
> This is likely to be the description of the "NameInSource" property. We incorrectly assign the same description to every other property. This is not helpful.
> Each property should have an accurate description that informs the user what the property represents. They should not have to do to the PDF documentation every time to look this information up - it's too tedious.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (TEIIDDES-382) Clicking on almost any model property results in incorrect description being displayed
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-382?page=com.atlassian.jira.plug... ]
Barry LaFond updated TEIIDDES-382:
----------------------------------
Fix Version/s: No Future
(was: 8.1)
> Clicking on almost any model property results in incorrect description being displayed
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-382
> URL: https://issues.jboss.org/browse/TEIIDDES-382
> Project: Teiid Designer
> Issue Type: Bug
> Components: Views
> Affects Versions: 7.4
> Reporter: Michael Walker
> Assignee: Dan Florian
> Priority: Minor
> Fix For: No Future
>
>
> Click on a property of a column. Below, you will see:
> i. NameInSource of Entity
> This is likely to be the description of the "NameInSource" property. We incorrectly assign the same description to every other property. This is not helpful.
> Each property should have an accurate description that informs the user what the property represents. They should not have to do to the PDF documentation every time to look this information up - it's too tedious.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (TEIIDDES-1425) Refactor > Rename of abstraction layer model was partially reflected in transformation
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1425?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1425:
-----------------------------------
Fix Version/s: 8.2
(was: 8.1)
> Refactor > Rename of abstraction layer model was partially reflected in transformation
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1425
> URL: https://issues.jboss.org/browse/TEIIDDES-1425
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.7.1
> Environment: JBDS 5.0 GA, SOA-tooling CR1
> Reporter: Paul Nittel
> Assignee: Barry LaFond
> Fix For: 8.2
>
> Attachments: RefactorRename_MPS.zip
>
>
> This project had a source model, abstraction layer (transformed from source), and a view model with a transformation. The transformation is essentially:
> SELECT * FROM vParts.Supplier AS s, vParts.Supplier_parts AS sp WHERE s.Supplier_id = sp.Supplier_id
> I added a second source and then used Refactor > Rename to change the original abstraction layer model from vParts to vParts_Oracle.
> The transformation was altered like this:
> SELECT * FROM vParts_Oracle.Supplier AS s, vParts.Supplier_parts AS sp WHERE s.Supplier_id = sp.Supplier_id
> So, it changed only the first instance of the model, leaving the transformation invalid.
> I'll attach a Model Project Set.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (TEIIDDES-1622) Sort out the refactoring framework
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1622?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1622:
-----------------------------------
Fix Version/s: 8.2
(was: 8.1)
> Sort out the refactoring framework
> ----------------------------------
>
> Key: TEIIDDES-1622
> URL: https://issues.jboss.org/browse/TEIIDDES-1622
> Project: Teiid Designer
> Issue Type: Enhancement
> Affects Versions: 8.1
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> The refactor actions (rename/move/rename-namespace/delete) have been organically developed and patched over the course of several years and as such lack a consistent approach in their operations.
> Re-implement the logic of each action using Eclipse's refactoring framework. This will include the following features as a standard part of the implementation:
> * Ties into Eclipse's history framework so resources can be restored to a previous state
> * Provides a UI so that the user can preview and accept the changes prior to them being performed
> * Sensible separation of condition-checking and actual operation
> * Functions in the same manner as existing Eclipse refactoring functionality
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (TEIIDDES-1636) Unable to create multiple source functions under one physical model in Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1636?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1636:
-----------------------------------
Attachment: CreatePushdownFunctionAction.java.patch
> Unable to create multiple source functions under one physical model in Teiid Designer
> -------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1636
> URL: https://issues.jboss.org/browse/TEIIDDES-1636
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.7
> Reporter: Debbie Steigner
> Fix For: 7.7.3
>
> Attachments: CreatePushdownFunctionAction.java.patch
>
>
> Unable to create multiple source functions under one physical model in EDS Teiid Designer. I want to create multiple source functions say LTRIM, RTRIM, TRUNC etc under one physical model and noticed that once I create the first source function by using (right click on model name -> New Child -> Create Source Function) the "Create Source Function" menu item is no longer available to create others.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (TEIIDDES-1636) Unable to create multiple source functions under one physical model in Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1636?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1636:
-----------------------------------
Fix Version/s: 7.7.3
> Unable to create multiple source functions under one physical model in Teiid Designer
> -------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1636
> URL: https://issues.jboss.org/browse/TEIIDDES-1636
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.7
> Reporter: Debbie Steigner
> Fix For: 7.7.3
>
> Attachments: CreatePushdownFunctionAction.java.patch
>
>
> Unable to create multiple source functions under one physical model in EDS Teiid Designer. I want to create multiple source functions say LTRIM, RTRIM, TRUNC etc under one physical model and noticed that once I create the first source function by using (right click on model name -> New Child -> Create Source Function) the "Create Source Function" menu item is no longer available to create others.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months