July 2011 - teiid-designer-issues

[JBoss JIRA] Assigned: (TEIIDDES-340) Update Incorrect When Changing Model Name On Last Page Of JDBC Wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-340?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-340: ------------------------------------- Assignee: Barry LaFond (was: Dan Florian) > Update Incorrect When Changing Model Name On Last Page Of JDBC Wizard > --------------------------------------------------------------------- > > Key: TEIIDDES-340 > URL: https://issues.jboss.org/browse/TEIIDDES-340 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Environment: Fedora 8 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: 7.5 > > > If you change step 3.3.2.1 of the E2E XML Book Set Mixed Test Script to select the project in the tree not the model, the model deltas are not calculated. Proceed as the test script says until the last page. Change the model name to match the update model and check "update." Now hit "Next >" to go to the last page and notice there are no differences when there should be since the foreign keys are being added. If you click "Finish" nothing is updated. This is because if go back in the wizard after changing the model name, the "Foreign Keys" and "Indexes" checkboxes are now unselected. I did not have this problem when running the same kit under MS Windows. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-689) Needs to be some indication to user that a data source needs to be created

by John Verhaeg (JIRA)

Needs to be some indication to user that a data source needs to be created -------------------------------------------------------------------------- Key: TEIIDDES-689 URL: https://jira.jboss.org/browse/TEIIDDES-689 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Affects Versions: 7.1 Reporter: John Verhaeg After creating one or more models and putting them in a VDB, there is no indication that the user needs to have a corresponding data source available on the server before they can successfully deploy that VDB. -- 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, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-968) Catalog and Schema should use different icons so that they can be distinquished as to their type

by Van Halbert (JIRA)

Catalog and Schema should use different icons so that they can be distinquished as to their type ------------------------------------------------------------------------------------------------ Key: TEIIDDES-968 URL: https://issues.jboss.org/browse/TEIIDDES-968 Project: Teiid Designer Issue Type: Enhancement Components: Modeling Affects Versions: 7.1.1 Reporter: Van Halbert Priority: Minor The catalog and schema should use different icons so that they can be distinguishable in the tree. The mouse-over type would also be helpful. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
17
0 / 0

[JBoss JIRA] Created: (TEIIDDES-999) Designer importing Teradata byteint data type as bigdecimal but it should be importing as byte data type

by Warren Gibson (JIRA)

Designer importing Teradata byteint data type as bigdecimal but it should be importing as byte data type -------------------------------------------------------------------------------------------------------- Key: TEIIDDES-999 URL: https://issues.jboss.org/browse/TEIIDDES-999 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.4 Reporter: Warren Gibson BQT booleanvalue has a source data type of byteint and Designer is importing it as a bigdecimal. It should be imported as a byte. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-998) Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system"

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-998?page=com.atlassian.jira.plug... ] Van Halbert moved SOA-3150 to TEIIDDES-998: ------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise SOA Platform) Key: TEIIDDES-998 (was: SOA-3150) Affects Version/s: 7.4 (was: 5.1.0 GA) Component/s: Import/Export (was: EDS) Security: (was: Public) > Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system" > --------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-998 > URL: https://issues.jboss.org/browse/TEIIDDES-998 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > > Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system" > When importing virtual procedure definitions it appears that its dependencies are not resolved. Given a file that contains: VProc1, "CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM ABC.DEF.MJA; END", "Some other description" They're treated as if the dependency doesn't exist, so one gets errors such as: Group does not exist: ABD.DEF.MJA The Base Table must reference 1 or more columns; there are none Cleaning the project doesn't appear to fix the problem. > Currently to resolve the above problem, you must "Validate Transformations", then "Build Imports", Save and Build All to have the errors resolved. The importer should do all of this, the customer should not have to perform these other manual steps -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-998) Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system"

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-998?page=com.atlassian.jira.plug... ] Van Halbert updated TEIIDDES-998: --------------------------------- Assignee: Barry LaFond Affects Version/s: 7.1.1 (was: 7.4) > Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system" > --------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-998 > URL: https://issues.jboss.org/browse/TEIIDDES-998 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > > Requesting more seamlessness in the Teiid Designer "Import Metadata from Text files on file system" > When importing virtual procedure definitions it appears that its dependencies are not resolved. Given a file that contains: VProc1, "CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM ABC.DEF.MJA; END", "Some other description" They're treated as if the dependency doesn't exist, so one gets errors such as: Group does not exist: ABD.DEF.MJA The Base Table must reference 1 or more columns; there are none Cleaning the project doesn't appear to fix the problem. > Currently to resolve the above problem, you must "Validate Transformations", then "Build Imports", Save and Build All to have the errors resolved. The importer should do all of this, the customer should not have to perform these other manual steps -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-996) Create Web Service fails if the model contains 2 schemas with the same tablenames underneath

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-996?page=com.atlassian.jira.plug... ] Ted Jones updated TEIIDDES-996: ------------------------------- Attachment: MySQL_Books.xmi Model with two schemas containing the same model name > Create Web Service fails if the model contains 2 schemas with the same tablenames underneath > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-996 > URL: https://issues.jboss.org/browse/TEIIDDES-996 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Ted Jones > Labels: eds > Fix For: 7.5 > > Attachments: MySQL_Books.xmi > > > In Teiid Designer, if you import a Source Model that contains 2 schemas, each schema contains tables with the same name. Right-click > Modeling > Create Web Service fails: > "The name table_a_OutputView is the same (ignoring case) as 1 other object(s) under the same parent." > The default names for the table Output Views should also contain the schema/folder names, i.e. schemaA_tableA_OutputView. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-960) StringNameValidator.createUniqueName() method is performing multiple unnecessary string operations

by Barry LaFond (JIRA)

StringNameValidator.createUniqueName() method is performing multiple unnecessary string operations -------------------------------------------------------------------------------------------------- Key: TEIIDDES-960 URL: https://issues.jboss.org/browse/TEIIDDES-960 Project: Teiid Designer Issue Type: Bug Components: Import/Export, Modeling Affects Versions: 7.4 Reporter: Barry LaFond Assignee: Dan Florian Fix For: 7.4 Discovered that StringNameValidator.createUniqueName() method is performing an interative existingName.toUpperCase() call. Importing BQT2 tables from SQL Server, for instance resulted in 2200+ calls to existingName.toUpperCase(). jdbc:sqlserver://slntdb02.mw.lab.eng.bos.redhat.com:1433;databaseName=bqt2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
9
0 / 0

[JBoss JIRA] Issue Comment Edited: (TEIIDDES-996) Create Web Service fails if the model contains 2 schemas with the same tablenames underneath

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-996?page=com.atlassian.jira.plug... ] Ted Jones edited comment on TEIIDDES-996 at 7/1/11 11:17 AM: ------------------------------------------------------------- TEIIDDES-968 will allow the user to import tables with fully qualified names (including schema) which will allow the user to create web services for models that have schemas with duplicate table names. was (Author: tejones): TEIIDDES-968 will allow the user to import tables with fully qualified names (including schema) which will the user to create web services for models that have schemas with duplicate table names. > Create Web Service fails if the model contains 2 schemas with the same tablenames underneath > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-996 > URL: https://issues.jboss.org/browse/TEIIDDES-996 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Ted Jones > Labels: eds > Fix For: 7.5 > > > In Teiid Designer, if you import a Source Model that contains 2 schemas, each schema contains tables with the same name. Right-click > Modeling > Create Web Service fails: > "The name table_a_OutputView is the same (ignoring case) as 1 other object(s) under the same parent." > The default names for the table Output Views should also contain the schema/folder names, i.e. schemaA_tableA_OutputView. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Issue Comment Edited: (TEIIDDES-996) Create Web Service fails if the model contains 2 schemas with the same tablenames underneath

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-996?page=com.atlassian.jira.plug... ] Ted Jones edited comment on TEIIDDES-996 at 7/1/11 11:13 AM: ------------------------------------------------------------- TEIIDDES-968 will allow the user to import tables with fully qualified names (including schema) which will the user to create web services for models that have schemas with duplicate table names. was (Author: tejones): This Jira will allow the user to import tables with fully qualified names (including schema) which will the user to create web services for models that have schemas with duplicate table names. > Create Web Service fails if the model contains 2 schemas with the same tablenames underneath > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-996 > URL: https://issues.jboss.org/browse/TEIIDDES-996 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Ted Jones > Labels: eds > Fix For: 7.5 > > > In Teiid Designer, if you import a Source Model that contains 2 schemas, each schema contains tables with the same name. Right-click > Modeling > Create Web Service fails: > "The name table_a_OutputView is the same (ignoring case) as 1 other object(s) under the same parent." > The default names for the table Output Views should also contain the schema/folder names, i.e. schemaA_tableA_OutputView. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2011