November 2011 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1120) Function's Return Parameter's context menu missing "Set Datatype" action

by Paul Nittel (Created) (JIRA)

Function's Return Parameter's context menu missing "Set Datatype" action ------------------------------------------------------------------------ Key: TEIIDDES-1120 URL: https://issues.jboss.org/browse/TEIIDDES-1120 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.4.2 Reporter: Paul Nittel Priority: Minor Attachments: ReturnParamNoContextSetType.png If you create a function model and to that a scalar function, a return parameter can only be given a type from the properties panel. There is no right-click context menu which allows setting datatypes for the return parameter. It's present for the parameters. See the attached screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-553) Finish adding the "Name:Type" capability to procedures and the new Function model type

by Paul Nittel (JIRA)

Finish adding the "Name:Type" capability to procedures and the new Function model type -------------------------------------------------------------------------------------- Key: TEIIDDES-553 URL: https://jira.jboss.org/browse/TEIIDDES-553 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 7.1 Environment: All Reporter: Paul Nittel When I'm modeling new relational models and creating columns, I can type the name of the column like "CoolColumnName:string(10)" and I not only get the column, I also get that its a String with a length of 10 characters. If I do that to a new Function model I get a column with the awkward name of "CoolColumnName:string(10)". Not valid! Please extend this valuable capability to other model type where applicable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-552) Function model should be automatically added to the VDB when a referencing model is added

by Paul Nittel (JIRA)

Function model should be automatically added to the VDB when a referencing model is added ----------------------------------------------------------------------------------------- Key: TEIIDDES-552 URL: https://jira.jboss.org/browse/TEIIDDES-552 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1 Environment: All Reporter: Paul Nittel Just like we automatically add XML Schema Documents (XSD) to a VDB when an XML document model is added, so should the function model when a referencing model is added. This will greatly increase the chance of first-time success! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-477) Relationship Navigator view Focus pull-down is incorrectly sized

by Paul Nittel (JIRA)

Relationship Navigator view Focus pull-down is incorrectly sized ---------------------------------------------------------------- Key: TEIIDDES-477 URL: https://jira.jboss.org/browse/TEIIDDES-477 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 7.0 Environment: Teiid Designer 7.0.0 running in JBDS 3.0.1 Reporter: Paul Nittel While playing in the Relationship world, I noticed the Focus pulldown in the Relationship Navigator view is too small to see anything, and does not resize, even when the view is maximized in Eclipse. See attached screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1071) Improve usability for primary end-to-end use cases

by Barry LaFond (JIRA)

Improve usability for primary end-to-end use cases -------------------------------------------------- Key: TEIIDDES-1071 URL: https://issues.jboss.org/browse/TEIIDDES-1071 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 7.5 Reporter: Barry LaFond Priority: Blocker Fix For: 7.6, 8.0 Basic modeling operations for Teiid Designer can confusing because of the wealth of options and lack of UI assistance. 1) Create Cheat Sheets for multi-step modeling processes 2) Create Advisor framework to assist user in monitoring progress through these steps 3) Create new customizable top-down view of workspace showing model dependencies and project/folder containment. - Allow drill-down editing ( EXAMPLE: Workspace > Project > Folder > Model > Table > Column ) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1069) The Wizard for Creating Web Service (SOAP and Non-SOAP) Needs Clarification

by Ted Jones (JIRA)

The Wizard for Creating Web Service (SOAP and Non-SOAP) Needs Clarification --------------------------------------------------------------------------- Key: TEIIDDES-1069 URL: https://issues.jboss.org/browse/TEIIDDES-1069 Project: Teiid Designer Issue Type: Quality Risk Components: Datatools Integration Affects Versions: 7.5 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.6 The wizard to create SOAP and non-SOAP connection profiles is not intuitive. We need to clarify this process and provide better documentation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-923) Passing NULL into a Procedure in Preview Causes Exception

by Ted Jones (JIRA)

Passing NULL into a Procedure in Preview Causes Exception --------------------------------------------------------- Key: TEIIDDES-923 URL: https://issues.jboss.org/browse/TEIIDDES-923 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 7.4 Reporter: Ted Jones I have a virtual procedure that accepts one parameter that may be null. When I pass a value in it works fine but when I check the NULL checkbox fir the input variable I get the following exception, "Remote org.teiid.api.exception.query.QueryValidatorException: Bind variables (represented as "?") were found but are allowed only in prepared or callable statements." Here is the generated query from preview: select * from ( exec RestfulBooks.getBooks(?) ) AS X_X -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
3
0 / 0

[JBoss JIRA] (TEIIDDES-1102) Improve the SQL Results View

by Mark Drilling (Created) (JIRA)

Improve the SQL Results View ---------------------------- Key: TEIIDDES-1102 URL: https://issues.jboss.org/browse/TEIIDDES-1102 Project: Teiid Designer Issue Type: Enhancement Components: Views Affects Versions: 7.4 Reporter: Mark Drilling Recommendations to improve the user experience with SQL Results view. Example screenshot will be attached. 1) When a query is successful, it should remain on the 'result' tab. Instead, the results table is displayed for a second - then it flips to the 'status' tab. It should stay on the results. An unsuccessful query should show the status and remain there. 2) The results are shown on a tab labeled 'Result1'. I don't see a way to get multiple result tabs. If that's the case, it should just be labeled 'Results' instead of 'Result1' 3) For Preview queries, the 'Connection Profile' column value is not user readable. It is something like 'Transient.org.teiid.datatools.connectivity.connectionProfile'. For previews, it should be something that makes sense to the user - maybe 'Preview - localhost - Teiid Connection' (to be consistent with other connectionProfile infos). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
10
0 / 0

[JBoss JIRA] Created: (TEIIDDES-882) Create new SOAP service connection profile.

by John Doyle (JIRA)

Create new SOAP service connection profile. ------------------------------------------- Key: TEIIDDES-882 URL: https://issues.jboss.org/browse/TEIIDDES-882 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.2, 7.1, 7.3 Reporter: John Doyle For the WSDL into Relational Model Importer we take advantage of the DTP provided Web Service Data Source connection profile. We really only did this because of time constraints. That profile has attributes that don't make sense for Teiid Designer and are ignored by Designer. We really need our own dedicated connection profile that provides the correct interface to the user and enables us to satisfy existing issues we cannot solve with the DTP profile. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
13
0 / 0

[JBoss JIRA] Created: (TEIIDDES-942) Need better indication of Error in Query Plan retrieval

by Mark Drilling (JIRA)

Need better indication of Error in Query Plan retrieval ------------------------------------------------------- Key: TEIIDDES-942 URL: https://issues.jboss.org/browse/TEIIDDES-942 Project: Teiid Designer Issue Type: Enhancement Components: Datatools Integration Affects Versions: 7.1.1 Reporter: Mark Drilling Priority: Minor It should be obvious to the user on the "Execution Plan" tab if a query error prevents retrieval of the Query Plan. - Executed a user query. The Execution Plan just showed the original SQL and nothing else... - Further examination of the server log showed plan debug output, but there was a source error on execution - I switched over to the "Message Log" tab in designer to find the message "An exception occurred fetching the Query Plan" Request that the Execution Plan tab show a problem message, instead of just showing the original SQL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2011