September 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-474) Extension Module attribute with name in camel case is shown as multiple words

by Paul Nittel (JIRA)

Extension Module attribute with name in camel case is shown as multiple words ----------------------------------------------------------------------------- Key: TEIIDDES-474 URL: https://jira.jboss.org/browse/TEIIDDES-474 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Environment: Designer 7.0.0 built 6/18/2010 Reporter: Paul Nittel I created an extension module, within that an extension package containing an XClass for a relational column, and, finally, with a single attribute: ShoeSize (an EInt). I associated this extension with a relational model (Parts) and viewed the PARTS.PARTS_ID column. There, I found, under Extensions, the attribute "Shoe Size"--with a space between "Shoe" and "Size". I don't know what ramifications might lie down the road, but it's definitely not the way it was input. -- 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

12 years

2
2
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

12 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

12 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

12 years

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-585) Remove XML Service metamodel as it is no longer used.

by Ken Johnson (JIRA)

Remove XML Service metamodel as it is no longer used. ----------------------------------------------------- Key: TEIIDDES-585 URL: https://jira.jboss.org/browse/TEIIDDES-585 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Environment: JBTools Aug 26, 2010. Eclipse 3.6, RHEL 6 Beta Reporter: Ken Johnson The XML Service metamodel is no longer used for sourcing XML data. It should be removed from Designer. -- 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

12 years, 3 months

2
1
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

12 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-620) Add Option for Embedded Teiid Connection vs JNDI in WAR Generation

by Ted Jones (JIRA)

Add Option for Embedded Teiid Connection vs JNDI in WAR Generation ------------------------------------------------------------------ Key: TEIIDDES-620 URL: https://jira.jboss.org/browse/TEIIDDES-620 Project: Teiid Designer Issue Type: Feature Request Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1.1 Need to allow for a embedded Teiid connection in the war generation process in addition to the current JNDI connection. This is required for HTTPBasic support. -- 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

12 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-530) The LDAP documentation in MMx that relates to designer activity, needs to be included in the designer documentation

by Van Halbert (JIRA)

The LDAP documentation in MMx that relates to designer activity, needs to be included in the designer documentation ------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-530 URL: https://jira.jboss.org/browse/TEIIDDES-530 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.0 Reporter: Van Halbert There is MMx LDAP documentation that relates to what has to be done in the designer in order to model a LDAP data source. This documentation needs to be brought over into designer documentation. -- 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

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-579) SQL Scrapbook created from Teiid connection is created with Ingress_2006 as the Connection Profile type.

by John Doyle (JIRA)

SQL Scrapbook created from Teiid connection is created with Ingress_2006 as the Connection Profile type. -------------------------------------------------------------------------------------------------------- Key: TEIIDDES-579 URL: https://jira.jboss.org/browse/TEIIDDES-579 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Affects Versions: 7.1 Reporter: John Doyle Assignee: John Doyle Fix For: 7.1 If you right click on a Teiid connection in the Data Source Explorer and open a SQL Scrapbook, the scrapbook page is not created with a Teiid Connection Profile Type, it is created with an Ingress_2006 type. -- 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

12 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-597) Insert Rows in relational column table editor creates columns in reverse order

by Paul Nittel (JIRA)

Insert Rows in relational column table editor creates columns in reverse order ------------------------------------------------------------------------------ Key: TEIIDDES-597 URL: https://jira.jboss.org/browse/TEIIDDES-597 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1 Environment: All Reporter: Paul Nittel Fix For: 7.1.1 Attachments: OutOfOrder.png (This has been an issue for a long time, but I don't see a current bug, so here's a new one!) If a user chooses to edit relational columnar metadata in teh table editor and Inserts Rows, they are inserted in reverse order. (See the attached screenshot.) In this case I inserted 8 rows. They're shown int eh tree in the correct order but arte inverted in the table editor. It's just wrong. -- 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

12 years, 8 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2010