July 2011 - teiid-designer-issues

[JBoss JIRA] Updated: (TEIIDDES-1009) Improve Designer "Metadata from Text files on file system" import option

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1009?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1009: ----------------------------------- Description: Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc. Also, change name to "Metadata from Flat or Text File" to distinguish it from "Metadata from Teiid Metadata File" was:Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc. > Improve Designer "Metadata from Text files on file system" import option > ------------------------------------------------------------------------ > > Key: TEIIDDES-1009 > URL: https://issues.jboss.org/browse/TEIIDDES-1009 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: eds > > Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc. > Also, change name to "Metadata from Flat or Text File" to distinguish it from "Metadata from Teiid Metadata File" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-1009) Teiid Designer "Import Metadata from Text files on file system" should allow for all metadata to be imported

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1009?page=com.atlassian.jira.plu... ] Van Halbert reassigned TEIIDDES-1009: ------------------------------------- Assignee: Barry LaFond (was: Van Halbert) > Teiid Designer "Import Metadata from Text files on file system" should allow for all metadata to be imported > ------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1009 > URL: https://issues.jboss.org/browse/TEIIDDES-1009 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: eds > > Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

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

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-311?page=com.atlassian.jira.plug... ] Mark Drilling resolved TEIIDDES-311. ------------------------------------ Resolution: Done Modified stylesheet to correct MySQL DDL export issues. > 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: 7.1.1 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 7.5 > > > 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1010: ---------------------------------------- A few things going on here. 1) Most legacy MM test DB tables with indexes use the "PK_<table name>" convention so name conflicts were pretty much non existent 2) The "ExcelModelProcessor" is the only class that actually implements the "modifyIndexName( IndexSpec indexSpec )" method for RelationalModelProcessorImpl and it looks for indexes named "PrimaryKey" and converts to a name that appends referenced column names 3) We need to create/add some test data that covers the "Multiple Schema" use-case as well as a Set of Tables that use duplicate primary key names across tables (i.e. use "PrimaryKey") > Indexes are not qualified when imported with Teiid Designer > ----------------------------------------------------------- > > Key: TEIIDDES-1010 > URL: https://issues.jboss.org/browse/TEIIDDES-1010 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Marc Shirley > Assignee: Barry LaFond > > Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

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

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-311?page=com.atlassian.jira.plug... ] Mark Drilling updated TEIIDDES-311: ----------------------------------- Fix Version/s: 7.5 Affects Version/s: 7.1.1 (was: Future) > 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: 7.1.1 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 7.5 > > > 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

13 years, 6 months

1
0
0 / 0

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

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-311?page=com.atlassian.jira.plug... ] Mark Drilling commented on TEIIDDES-311: ---------------------------------------- Yes, this is still an issue. I created a BQT project in Designer by importing from an Oracle BQT instance. Then exported the DDL and tried to run it against a MySQL 5.5 database. Ran into a couple issues which prevented import: 1- Create table syntax for FLOAT columns failed. "FLOATNUM FLOAT", and "FLOATNUM FLOAT(126,5)" are valid for example but not "FLOATNUM FLOAT(126)" 2- Create table syntax "CHARVALUE CHAR(1) DEFAULT('1')" failed, should be "CHARVALUE CHAR(1) DEFAULT '1'" There may be more issues, these are the first two I hit... Syntax reference is at http://dev.mysql.com/doc/refman/5.1/en/create-table.html > 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

13 years, 6 months

1
0
0 / 0

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

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-311?page=com.atlassian.jira.plug... ] Work on TEIIDDES-311 started by Mark Drilling. > 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1012) Search Exception is encountered - on attempt to search with open XSD Model

by Mark Drilling (JIRA)

Search Exception is encountered - on attempt to search with open XSD Model -------------------------------------------------------------------------- Key: TEIIDDES-1012 URL: https://issues.jboss.org/browse/TEIIDDES-1012 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 7.1.1 Reporter: Mark Drilling Search fails with the attached stack trace, if an XSD model is open for editing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
3
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1010: --------------------------------------- I think the indexes should be under the table. This will solve 2 issues: uniqueness and the usability issue of having all the indexes in the tree > Indexes are not qualified when imported with Teiid Designer > ----------------------------------------------------------- > > Key: TEIIDDES-1010 > URL: https://issues.jboss.org/browse/TEIIDDES-1010 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Marc Shirley > Assignee: Barry LaFond > > Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1011) Indexes are not qualified when imported with Teiid Designer

by Van Halbert (JIRA)

Indexes are not qualified when imported with Teiid Designer ----------------------------------------------------------- Key: TEIIDDES-1011 URL: https://issues.jboss.org/browse/TEIIDDES-1011 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.4 Reporter: Marc Shirley Assignee: Barry LaFond Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2011