January 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-685) XML-Relational models should be flagged as invalid in Teiid Designer 7.X

by John Doyle (JIRA)

XML-Relational models should be flagged as invalid in Teiid Designer 7.X ------------------------------------------------------------------------ Key: TEIIDDES-685 URL: https://jira.jboss.org/browse/TEIIDDES-685 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 7.1, 7.0 Reporter: John Doyle Assignee: John Doyle The XML-Relational connectors were removed from Teiid and therefore the XML-Relational models are no longer valid artifacts. For model projects created in earlier versions of Designer with XML-Relational models, we should recognize those models (through their model extensions) and flag them as invalid. The message should provide the user with a pointer to the new way to integrate with xml/web services. -- 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

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-811) NPE while loading the example project

by Ramesh Reddy (JIRA)

NPE while loading the example project ------------------------------------- Key: TEIIDDES-811 URL: https://issues.jboss.org/browse/TEIIDDES-811 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Environment: JBDS Beta2 Reporter: Ramesh Reddy > java.lang.NullPointerException > at org.eclipse.ui.wizards.datatransfer.ImportOperation.importRecursivelyFrom(ImportOperation.java:789) > at org.eclipse.ui.wizards.datatransfer.ImportOperation.importFileSystemObjects(ImportOperation.java:674) > at org.eclipse.ui.wizards.datatransfer.ImportOperation.execute(ImportOperation.java:407) > at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) > at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) > at org.jboss.tools.project.examples.wizard.NewProjectExamplesWizard.importProject(NewProjectExamplesWizard.java:591) > at org.jboss.tools.project.examples.wizard.NewProjectExamplesWizard$2.runInWorkspace(NewProjectExamplesWizard.java:183) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-808) Provide the ability to name the Teiid instance for better reference in error messaging.

by Barry LaFond (JIRA)

Provide the ability to name the Teiid instance for better reference in error messaging. --------------------------------------------------------------------------------------- Key: TEIIDDES-808 URL: https://issues.jboss.org/browse/TEIIDDES-808 Project: Teiid Designer Issue Type: Enhancement Components: Teiid Integration, VDB & Execution Affects Versions: 7.2, 7.1.1 Reporter: Barry LaFond Assignee: Dan Florian Fix For: 7.3 Provide the ability to name the Teiid instance for better reference in error messaging. In jira TEIIDDES-283, when that is fixed, it would be good if it utilized the name of the Teiid instance in the error message. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-791) Create a Web Service Model Example

by Ted Jones (JIRA)

Create a Web Service Model Example ---------------------------------- Key: TEIIDDES-791 URL: https://issues.jboss.org/browse/TEIIDDES-791 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.1.1 Reporter: Ted Jones Assignee: John Doyle Priority: Blocker Fix For: 7.1.1 There is an EDS requirement for a WS-=Relational example. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (TEIIDDES-805) Fix General Preference Contributor EXSD Errors

by Dan Florian (JIRA)

Fix General Preference Contributor EXSD Errors ---------------------------------------------- Key: TEIIDDES-805 URL: https://issues.jboss.org/browse/TEIIDDES-805 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.2 Reporter: Dan Florian Fix For: 7.3 Attachments: TEIIDDES-805.patch The following errors in org.teiid.designer.ui/generalPreferenceContributor.exsd should be fixed: 1. Reference element 'description' is not defined 2. Reference element 'primaryWizard' is not defined 3. Reference element 'selection' is not defined -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-734) Create a WS-Relational Example

by John Doyle (JIRA)

Create a WS-Relational Example ------------------------------ Key: TEIIDDES-734 URL: https://issues.jboss.org/browse/TEIIDDES-734 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.1.1 Reporter: John Doyle Assignee: John Doyle Priority: Blocker Fix For: 7.1.1 There is an EDS requirement for a WS-=Relational example. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-464) Teiid 7.0 XML integration issues

by Steve Hawkins (JIRA)

Teiid 7.0 XML integration issues -------------------------------- Key: TEIIDDES-464 URL: https://jira.jboss.org/browse/TEIIDDES-464 Project: Teiid Designer Issue Type: Quality Risk Components: Import/Export, Modeling, Teiid Integration Affects Versions: 7.0 Reporter: Steve Hawkins Priority: Critical With Teiid 7.0 there are several changes that affect functionality provided in the designer: 1. The xml imports (relational or source) are now invalid. There is now engine functionality to handle row extraction. If possible these importers should be retargeted. 2. The xquery web services model is now invalid. XQuery is now executed through the XMLQUERY expression, so the command type is just regular SQL - not XQuery. -- 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

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-536) JDBC importer should offer to widen unsigned types

by Steve Hawkins (JIRA)

JDBC importer should offer to widen unsigned types -------------------------------------------------- Key: TEIIDDES-536 URL: https://jira.jboss.org/browse/TEIIDDES-536 Project: Teiid Designer Issue Type: Quality Risk Components: Import/Export Affects Versions: 7.1 Reporter: Steve Hawkins Some databases support unsigned types (mysql) and others such as Sybase/SQLServer have types, tinyint, that are unsigned and do not map naturally to the corresponding signed teiid type. The importer should offer to widen theses types, e.g. tinyint becomes a short instead of a byte. -- 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

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-774) Add support for "for each row" update procedures and new default handling

by Steven Hawkins (JIRA)

Add support for "for each row" update procedures and new default handling ------------------------------------------------------------------------- Key: TEIIDDES-774 URL: https://issues.jboss.org/browse/TEIIDDES-774 Project: Teiid Designer Issue Type: Feature Request Components: Modeling, Teiid Integration Affects Versions: 7.3 Reporter: Steven Hawkins Fix For: 7.3 Teiid now has support for "for each row" procedures that can be used instead of update procedures. The initial plan is to support both our old update procedures and the new for each row handling. Default update handling has has been updated to no longer require a procedure - Teiid in fact expects a null value to indicate a default procedure. In dev emails it was brought up that the specific insert/update/delete enabled toggle may not be needed anymore given the improvement in the default handling. One possibility is to change its meaning to something like "must be updatable". In which case the validation problems will need to be separated out by procedure type and then elevated to errors. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-215) Autoincrement incorrectly imported for SQL Server 2008

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-215?page=com.atlassian.jira.plug... ] Barry LaFond commented on TEIIDDES-215: --------------------------------------- SQL Server 2000 docs states: "The IDENTITY property can be assigned to tinyint, smallint, int, bigint, decimal(p,0), or numeric(p,0) columns." So we need to take these other datatypes into account. Also, after converting the datatype during the import, we'll need to make sure the exported DDL is generated back as "int identity" > Autoincrement incorrectly imported for SQL Server 2008 > ------------------------------------------------------ > > Key: TEIIDDES-215 > URL: https://issues.jboss.org/browse/TEIIDDES-215 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.1.0 > Environment: Windows XP, Eclipse 3.4.2, SQL Server 2008, JDBC driver by Microsoft > Reporter: Michael Riedmueller > Assignee: Barry LaFond > Fix For: 7.3 > > > Table attributes with type int and autoincrement set to true are imported with data type "int identity", autoincrement is NOT set in the properties. > This should be data type "int" and autoincrement set to true. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 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 2011