January 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-293) WSDL to Relational Model Importer: WSDL imports into model with incorredt types and column names.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-293?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-293: ---------------------------------- Fix Version/s: 7.7.1 > WSDL to Relational Model Importer: WSDL imports into model with incorredt types and column names. > ------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-293 > URL: https://issues.jboss.org/browse/TEIIDDES-293 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1, 7.2, 7.3 > Reporter: John Doyle > Assignee: Barry LaFond > Labels: wsdltorelational > Fix For: 7.7.1 > > Attachments: TmsWebService.wsdl > > > The attached WSDL causes an NPE when the model objects are being created. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-280) Update Count metadata property is not avaialble on the Web Service procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-280?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-280: ---------------------------------- Fix Version/s: 7.7.1 > Update Count metadata property is not avaialble on the Web Service procedure > ---------------------------------------------------------------------------- > > Key: TEIIDDES-280 > URL: https://issues.jboss.org/browse/TEIIDDES-280 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Ramesh Reddy > Fix For: 7.7.1 > > > "Update Count" metadata is not available on the Web Service procedure, this is only available on the virtual procedures. This data is used at run time to determine if procedure is "readonly", or does "single" or "multiple" updates to the underlaying databases. If this property not available then by default it is assumed that "multiple" updates and subject to the transactional restrictions in the server and dqp. > Per SteveH, this property must be on any kind of procedure, may that be virtual, web and xml service. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-276) improve WSDL importer accuracy

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-276?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-276: ---------------------------------- Fix Version/s: 7.7.1 > improve WSDL importer accuracy > ------------------------------- > > Key: TEIIDDES-276 > URL: https://issues.jboss.org/browse/TEIIDDES-276 > Project: Teiid Designer > Issue Type: Task > Components: Import/Export > Reporter: Marc Shirley > Fix For: Future, 7.7.1 > > > are we trying to do too much ourselves instead of leveraging some standard open source components - seems like somebody must have solved the problem of turn WSDL into accurate Java object heirarchy, and we can go from there... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-191) XSD as Relational importer has problems with child elements with many parents

by Greg Haber (JIRA)

XSD as Relational importer has problems with child elements with many parents ----------------------------------------------------------------------------- Key: TEIIDDES-191 URL: https://jira.jboss.org/jira/browse/TEIIDDES-191 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: Teiid Designer 6.0.0 official (14 May 2009) release Reporter: Greg Haber Attachments: address.xsd, person.xsd, person2.xml, person2.xsd I've encountered a lot of problems with the Teiid Designer XML as Relational Importer (and with its legacy ancestor) dealing with importing XSDs where a child element has multiple parents. The importer currently treats all elements throughout the XSD that have the same name and type as the same, and so models that element(s) as a single table with multiple parents, if the number of parents is above a configurable number (currently defaults to 3). Which is all well and good in theory, but in practice it seems to hit a number of problems 1) During the import process, if the selection of document root elements is left at the default, not all needed tables are generated. See person.xsd example attached. 2) If all possible root elements are selected, it looks mostly right, but there are often extra elements in the child tables (again try with person.xsd). Plus, the tables don't actually work at runtime correctly (try using attached person2.xml as the data source - notice that you can only get to the spouse's father from Person, not to their own father). I've also attached some other example problem XSDs - person2.xsd, and address.xsd Now, in some cases a reasonable workaround is to up the number of allowed parents parameter, so that everything gets folded into a single table. But that isn't a general solution, as it doesn't work with things like person2.xsd. -- 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

14 years, 3 months

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-1211) Exporting DDL for Postgres produces invalid CREATE INDEX statement because duplicate object names in database

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-1211: ------------------------------------- Summary: Exporting DDL for Postgres produces invalid CREATE INDEX statement because duplicate object names in database Key: TEIIDDES-1211 URL: https://issues.jboss.org/browse/TEIIDDES-1211 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.4.2 Reporter: Van Halbert Attachments: tpc_postgres.ddl Trying to execute DDL on postgres database produces this error: Error: ERROR: relation "orders" already exists SQLState: 42P07 ErrorCode: 0 Error occured in: CREATE INDEX ORDERS ON ORDERS (O_CUSTKEY) ---- The problem was resolved if I changed ORDERS index name: CREATE INDEX ORDERS ON ORDERS (O_CUSTKEY); ---- Here's a statement I found on the Postgres Naming rules: The names of all objects must be unique within some scope. Every database must have a unique name; the name of a schema must be unique within the scope of a single database, the name of a table must be unique within the scope of a single schema, and column names must be unique within a table. The name of an index must be unique within a database. I would like to suggest that all index names that are created are appended with "idx" or something similar. Right now, the first looks to be the name of the table, and subsequent names have 1,2, etc. appended. -- 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, 3 months

2
6
0 / 0

[JBoss JIRA] (TEIIDDES-1205) Reminder to deprecate the old extension framework for later removal

by Van Halbert (Created) (JIRA)

Reminder to deprecate the old extension framework for later removal ------------------------------------------------------------------- Key: TEIIDDES-1205 URL: https://issues.jboss.org/browse/TEIIDDES-1205 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.7 Reporter: Van Halbert Priority: Critical Fix For: 7.7 Deprecate the old extension framework so that it can be removed in a later release (i.e, 8.0). -- 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, 3 months

4
7
0 / 0

[JBoss JIRA] (TEIIDDES-1175) Importing a new model when an existing model is selected in the modeler tree works, but leaves old model info in Data Source props

by Paul Nittel (Created) (JIRA)

Importing a new model when an existing model is selected in the modeler tree works, but leaves old model info in Data Source props ---------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1175 URL: https://issues.jboss.org/browse/TEIIDDES-1175 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.6 Environment: Fedora 16 Reporter: Paul Nittel Attachments: ShouldBeOracleSourceInfo.png I imported from a DB2 source. With that model selected, I right-clicked elsewhere in the Model Explorer tree and imported a different model. At the last page of the import wizard, the previously-selected model was the targeted name for this new model. I unchecked update and changed the name of the model to reflect what was being imported. After the import had completed, the Data Source item for the imported model had the information from the old model which had been selected in the tree. See 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, 3 months

5
5
0 / 0

[JBoss JIRA] (TEIIDDES-1027) CLONE - Allow for the parsing of fixed width files that don't use delimiters.

by Barry LaFond (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1027?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1027. ------------------------------------ Resolution: Done Added NO TRIM option to TEXTTABLE() function options dialog > CLONE - Allow for the parsing of fixed width files that don't use delimiters. > ----------------------------------------------------------------------------- > > Key: TEIIDDES-1027 > URL: https://issues.jboss.org/browse/TEIIDDES-1027 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.6 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.7 > > Attachments: edit-texttable-function-options-dialog.png > > > Parsing a fixed width file that does not use a delimiter, or uses a newline for wrapping, is not currently possible. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1027) CLONE - Allow for the parsing of fixed width files that don't use delimiters.

by Barry LaFond (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1027?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1027: ----------------------------------- Attachment: edit-texttable-function-options-dialog.png > CLONE - Allow for the parsing of fixed width files that don't use delimiters. > ----------------------------------------------------------------------------- > > Key: TEIIDDES-1027 > URL: https://issues.jboss.org/browse/TEIIDDES-1027 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.6 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.7 > > Attachments: edit-texttable-function-options-dialog.png > > > Parsing a fixed width file that does not use a delimiter, or uses a newline for wrapping, is not currently possible. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1027) CLONE - Allow for the parsing of fixed width files that don't use delimiters.

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1027?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1027: ------------------------------------------ Yes, that is ok. It is only needed in delimited mode and you could add to the tip that it is only needed if the column has non-quoted values. > CLONE - Allow for the parsing of fixed width files that don't use delimiters. > ----------------------------------------------------------------------------- > > Key: TEIIDDES-1027 > URL: https://issues.jboss.org/browse/TEIIDDES-1027 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.6 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.7 > > > Parsing a fixed width file that does not use a delimiter, or uses a newline for wrapping, is not currently possible. -- 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, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2012