August 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-189) Plugin details shows version, but not build number

by Paul Nittel (JIRA)

Plugin details shows version, but not build number -------------------------------------------------- Key: TEIIDDES-189 URL: https://jira.jboss.org/jira/browse/TEIIDDES-189 Project: Teiid Designer Issue Type: Bug Components: Build Affects Versions: 6.0.0 Environment: Fedora 10 Reporter: Paul Nittel Since the plugin details shows only the version (6.0.0), there is no way to determine from which build this came. We really need this ability back. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-171) VDB Editor allows adding multiple Salesforce generated relational models.

by Barry LaFond (JIRA)

VDB Editor allows adding multiple Salesforce generated relational models. ------------------------------------------------------------------------- Key: TEIIDDES-171 URL: https://jira.jboss.org/jira/browse/TEIIDDES-171 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 6.0.0 Reporter: Barry LaFond Fix For: 6.1.0 While investigating TEIIDDES-168, I tried to add a second Salesforce model to a VDB. I had already added "sf.xmi" which auto-added the XMLSOAPConnectorExtensions.xmi model. But adding "stock.xmi", which depends on a DIFFERENT XMLSOAPConnectorExtensions.xmi file, it added "stock.xmi" thinking it already had the right XMLSOAPConnectorExtensions.xmi file. So, there is a bug here where VDB Editor should have detected the actual dependent XMLSOAPConnectorExtensions.xmi file and NOT allowed adding stock.xmi -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-126) Add a warning for the use of a model supports property

by Steven Hawkins (JIRA)

Add a warning for the use of a model supports property ------------------------------------------------------ Key: TEIIDDES-126 URL: https://jira.jboss.org/jira/browse/TEIIDDES-126 Project: Teiid Designer Issue Type: Quality Risk Components: Modeling Affects Versions: 6.0.0 Reporter: Steven Hawkins See TEIID-131. Model support properties that are simply overrides for connector binding properties are no longer checked by the Teiid runtime, rather TEIID-205 is used to control specific capabilities through the connector binding without requiring the creation of a custom capabilities class. Usage of 'Set Criteria Max Size', Supports "Distinct', Supports "Join", Supports "Order By", Supports "Outer Join", and Supports "Where all" should generate a warning stating that the connector binding should be used instead. -- 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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-417) Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled

by Paul Nittel (JIRA)

Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled --------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-417 URL: https://jira.jboss.org/jira/browse/TEIIDDES-417 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.3 Environment: Iced Tea, Teiid Designer 6.3 Reporter: Paul Nittel Attachments: IMFTF.jpg I was writing a SWTBot test to create a view model's tables when I ran into this. Knowing SWTBot can't handle the File Chooser, I was delighted to see I could enter the text file's path and name directly into the importer dialog. It wasn't until some time later that I realized merely typing in the name does nothing; you MUST enter the name using the File Chooser. (Once that's been done, it appears you can use the drop-down to re-select that file, but you need that first time entry.) What's really bad/confusing is manually entering the file and target location enables the Finish button. Clicking it appears to work, but no tables were added to the model. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-466) WSDL Generation from Web Service Models Creates Extraneous Nodes

by Ted Jones (JIRA)

WSDL Generation from Web Service Models Creates Extraneous Nodes ---------------------------------------------------------------- Key: TEIIDDES-466 URL: https://jira.jboss.org/browse/TEIIDDES-466 Project: Teiid Designer Issue Type: Task Components: Modeling Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.0 Generated web service models from a Books VDB which creates operations for getBooks, getAuthors, getBooks_Authors, and getPublishers. A separate port type, binding and port is generated for each operation. Only one port type, binding and port is needed. We should get rid of the extraneous nodes and combine into one port type, binding and port. -- 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

13 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-518) DTP context menu options on Teiid tables should consider whether virtual model supports update.

by Ken Johnson (JIRA)

DTP context menu options on Teiid tables should consider whether virtual model supports update. ----------------------------------------------------------------------------------------------- Key: TEIIDDES-518 URL: https://jira.jboss.org/browse/TEIIDDES-518 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.0 Environment: Teiid Designer 7.0 + JBoss Dev Studio 3.0.1GA Teiid 7.1 Alpha on EAP 5.1 RHEL 6, OpenJDK 1.6 Reporter: Ken Johnson In DTP, Context menu for Table contains several options under Data->(Edit, Load, Extract, Sample Contents). For virtual tables, Extract and Sample Contents are fine. Edit and Load will attempt to write data. Thus a few issues: a) These options should be disabled if the table in question does not have Supports Update checked. b) These options should be tested when the table *does* have Update and Insert procedures defined. c) Tables in SYS schema should never be writable. When working with physical tables, all options should be available and work correctly. Cursory testing indicates this is the case - at least with a MySQL data source underlying the model. -- 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

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-268) "Create Web Service" wizard on a virtual procedure produces invalid SQL in transformation

by Debbie Steigner (JIRA)

"Create Web Service" wizard on a virtual procedure produces invalid SQL in transformation ----------------------------------------------------------------------------------------- Key: TEIIDDES-268 URL: https://jira.jboss.org/jira/browse/TEIIDDES-268 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.0 Reporter: Debbie Steigner Fix For: 7.0 If you use our "Create Web Service" wizard on a virtual procedure the SQL transformation for the Output View is invalid for the current product. For example, our wizard produced: SELECT * FROM (EXEC TwoStepsFeatureTable.TwoSteps(left_node = left_node)) AS TwoSteps so it errors on left_node: Resolver Error: Symbol left_node is specified with an unknown group context The transformation should be procedural relational instead: SELECT * FROM TwoStepsFeatureTable.TwoSteps -- 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

13 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-210) Add implicit conversion of NULL to correct datatype in transformation validator

by Marc Shirley (JIRA)

Add implicit conversion of NULL to correct datatype in transformation validator ------------------------------------------------------------------------------- Key: TEIIDDES-210 URL: https://jira.jboss.org/jira/browse/TEIIDDES-210 Project: Teiid Designer Issue Type: Feature Request Components: Transformations, Validation Affects Versions: 6.0.0, 6.1.0 Reporter: Marc Shirley When using NULL value as a column (ie, NULL as columnName), it is only implicitly converted to a string. When trying to use the NULL as a column of type date, integer, float, etc., the validator throws a warning that the transformation is not valid. If you wrap the NULL in a convert to the correct column datatype (ie, "convert(NULL,date)"), the transformation can be validated successfully. -- 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

13 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-188) Database Schema not used in sql query

by Ben Truitt (JIRA)

Database Schema not used in sql query ------------------------------------- Key: TEIIDDES-188 URL: https://jira.jboss.org/jira/browse/TEIIDDES-188 Project: Teiid Designer Issue Type: Bug Environment: Ubuntu 9.x eclipse 3.4.2 teiid_designer_6.0.0.v20090427_SNAPSHOT Postgresql 8.2 postgresql-8.3-604.jdbc4.jar Reporter: Ben Truitt It looks like the database schema specified in the XMI file for the model is not being used when generating the SQL query to preview data from the model. I'm attaching my model XMI file. Note the schema is named "rollback". However, the SQL query generated does not include the schema name, instead it only includes the table name. -- 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

13 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-304) External metadata needs to be marked as scalar groups where appropriate

by Van Halbert (JIRA)

External metadata needs to be marked as scalar groups where appropriate ----------------------------------------------------------------------- Key: TEIIDDES-304 URL: https://jira.jboss.org/jira/browse/TEIIDDES-304 Project: Teiid Designer Issue Type: Task Components: Modeling Reporter: Van Halbert Priority: Minor Fix For: 7.1 External temp metadata supplied by the designer should be marked as coming from a scalar group for INPUT, CHANGING, and VARIABLES groups. -- 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

13 years, 2 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2010