July 2011 - teiid-designer-issues

[JBoss JIRA] Assigned: (TEIIDDES-333) "Update cost statistics" action should indicate a change in the model that requires a save, but it does not do so

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-333?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-333: ------------------------------------- Assignee: Barry LaFond > "Update cost statistics" action should indicate a change in the model that requires a save, but it does not do so > ----------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-333 > URL: https://issues.jboss.org/browse/TEIIDDES-333 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Reporter: Michael Walker > Assignee: Barry LaFond > Priority: Minor > > Create a source model and save it. Then run "update cost statistics". The cost stat properties will be updated in the model. However, the model will remain "unchanged" in that there's no indication that it needs to be saved. Users can then accidentally close Designer and lose the changes, execute it in a VDB and get unexpected results, etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-332) New virtual procedures should always contain the prologue/postlogue, rather than require the user to remember the syntax

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-332?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-332. ----------------------------------- Resolution: Done Added initial SQL value of : CREATE VIRTUAL PROCEDURE BEGIN <--insert SQL here-->; END > New virtual procedures should always contain the prologue/postlogue, rather than require the user to remember the syntax > ------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-332 > URL: https://issues.jboss.org/browse/TEIIDDES-332 > Project: Teiid Designer > Issue Type: Feature Request > Components: Transformations > Affects Versions: 7.4 > Reporter: Michael Walker > Assignee: Barry LaFond > Priority: Minor > Fix For: 7.5 > > > When you create a new virtual procedure, you should automatically get this in the transformation editor: > CREATE VIRTUAL PROCEDURE > BEGIN > -- insert transformation logic here > END > Instead, we expect the user to remember this syntax, which is a very common source of mistakes. > As an alternative, we could hide this from the user completely, and maintain this standard stuff internally. This would reduce the # lines of code required to display on screen, and eliminate the possibility of mis-editing this stuff later. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-332) New virtual procedures should always contain the prologue/postlogue, rather than require the user to remember the syntax

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-332?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-332: ---------------------------------- Fix Version/s: 7.5 Affects Version/s: 7.4 > New virtual procedures should always contain the prologue/postlogue, rather than require the user to remember the syntax > ------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-332 > URL: https://issues.jboss.org/browse/TEIIDDES-332 > Project: Teiid Designer > Issue Type: Feature Request > Components: Transformations > Affects Versions: 7.4 > Reporter: Michael Walker > Assignee: Barry LaFond > Priority: Minor > Fix For: 7.5 > > > When you create a new virtual procedure, you should automatically get this in the transformation editor: > CREATE VIRTUAL PROCEDURE > BEGIN > -- insert transformation logic here > END > Instead, we expect the user to remember this syntax, which is a very common source of mistakes. > As an alternative, we could hide this from the user completely, and maintain this standard stuff internally. This would reduce the # lines of code required to display on screen, and eliminate the possibility of mis-editing this stuff later. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-332) New virtual procedures should always contain the prologue/postlogue, rather than require the user to remember the syntax

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-332?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-332: ------------------------------------- Assignee: Barry LaFond > New virtual procedures should always contain the prologue/postlogue, rather than require the user to remember the syntax > ------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-332 > URL: https://issues.jboss.org/browse/TEIIDDES-332 > Project: Teiid Designer > Issue Type: Feature Request > Components: Transformations > Reporter: Michael Walker > Assignee: Barry LaFond > Priority: Minor > > When you create a new virtual procedure, you should automatically get this in the transformation editor: > CREATE VIRTUAL PROCEDURE > BEGIN > -- insert transformation logic here > END > Instead, we expect the user to remember this syntax, which is a very common source of mistakes. > As an alternative, we could hide this from the user completely, and maintain this standard stuff internally. This would reduce the # lines of code required to display on screen, and eliminate the possibility of mis-editing this stuff later. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-311) The exported DDL for MySQL does not work when trying to run it agains the database

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-311?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-311: ------------------------------------- Assignee: Mark Drilling Verify whether this works yet or not > The exported DDL for MySQL does not work when trying to run it agains the database > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-311 > URL: https://issues.jboss.org/browse/TEIIDDES-311 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: Future > Reporter: Van Halbert > Assignee: Mark Drilling > > The exported DDL for mysql did not work in either MySql versions 4 or 5. What trying to create the BQT tables. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-310) Query Plan Viewer "expand" button should expand all nodes by default

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-310?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-310. ----------------------------------- Assignee: Barry LaFond Resolution: Won't Fix SQL Explorer and related views including Query Plan view are no longer part of Designer. Replaced by Data Tools Functionality > Query Plan Viewer "expand" button should expand all nodes by default > -------------------------------------------------------------------- > > Key: TEIIDDES-310 > URL: https://issues.jboss.org/browse/TEIIDDES-310 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Michael Walker > Assignee: Barry LaFond > Priority: Optional > > When viewing a deep query tree, it is tedious to individually click each node to expand it, before finally getting to the access nodes. Perhaps we should default to expanding the entire tree. This is an optional usability improvement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-294) Query Plan Viewer in Designer does not fully display source queries in the bottom panel if it is long

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-294?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-294. --------------------------------- > Query Plan Viewer in Designer does not fully display source queries in the bottom panel if it is long > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-294 > URL: https://issues.jboss.org/browse/TEIIDDES-294 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Michael Walker > Assignee: Barry LaFond > Attachments: queryplantruncation.JPG, queryplantruncation2.JPG > > > Query Plan Viewer in Designer does not fully display source queries in the bottom panel if it is long. See screenshot for example. First screenshot shows the beginning of the source query, second screenshot shows that the source query is truncated when I scroll all the way to the right. > We should show the entire query. > This problem also occurs on Access nodes on the top-half of the query planner. However, you can double-click to view the entire query. This double-click capability is not available on the bottom half for some reason. Perhaps we should add it. > There are some cases where source queries are not displayed in the top-half (query plan screen) but do appear in the bottom half only. In those cases, there's no way to view the entire source query using this editor. Workaround is to view the XML query plan. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-274) Make it easier to double-click to drill down into the transformation for a given view model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-274?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-274. --------------------------------- > Make it easier to double-click to drill down into the transformation for a given view model > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-274 > URL: https://issues.jboss.org/browse/TEIIDDES-274 > Project: Teiid Designer > Issue Type: Feature Request > Components: Diagrams > Affects Versions: Future > Reporter: Michael Walker > Assignee: Barry LaFond > Attachments: deadarea.JPG > > Time Spent: 1 minute > Remaining Estimate: 0 minutes > > We have allocated a very small area of space on each view model that allows you to double-click and drill down into the transformation, but it's too difficult for new users to locate this area, and there's no visual indication of where it begins or ends. > This is very common issue among new Designer users. They want to double-click on a view, to display and/or edit its transformation. They try double-clicking on the middle of the view -- this highlights the columns and does not drill-down. They try clicking on the top of the view, on it's name -- this highlights the view name and does not drill-down. If they happen to leave the view or column highlighted, then they won't be able to drill-down, even if they do click the small area that allows for it. > They give up on double-clicking, and instead, right-click on the view and get a large menu of options. "Open" is buried about half-way down, so some of them don't have the patience to find it. Overall, the process is very frustrating for new users. We should make it much more straightforward to do common operations such as this one. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-260) Problems in New Model Wizard after backing up to Select different Metamodel type

by Barry LaFond (JIRA)

Problems in New Model Wizard after backing up to Select different Metamodel type -------------------------------------------------------------------------------- Key: TEIIDDES-260 URL: https://jira.jboss.org/jira/browse/TEIIDDES-260 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 Open Designer and make sure you have a Relational and Web service model in workspace (i.e. import relational and create WS via "Modeling >> Create Web Service" action. 1) Select "New Metadata Model" 2) Select "Relational" metamodel and "Source" model type (click NEXT) 3) Select Relational model in workspace (via "..." browse button) (notice selecting non-relational models results in error message in model selection dialog) (click OK) 4) Select "Back" button to return to selecting model types 5) Select "Web Service" metamodel (click NEXT) 6) Select Web Service model in workspace (via "..." browse button). 7) Note that error message says that user must select a "Relational" model. This is wrong and basically the MetaModelDescriptor isn't getting updated on the StructuralCopyWizard & TreeViewerWizardPanel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
3
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-310) Query Plan Viewer "expand" button should expand all nodes by default

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-310?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-310. --------------------------------- > Query Plan Viewer "expand" button should expand all nodes by default > -------------------------------------------------------------------- > > Key: TEIIDDES-310 > URL: https://issues.jboss.org/browse/TEIIDDES-310 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Michael Walker > Assignee: Barry LaFond > Priority: Optional > > When viewing a deep query tree, it is tedious to individually click each node to expand it, before finally getting to the access nodes. Perhaps we should default to expanding the entire tree. This is an optional usability improvement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2011