July 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-518) DTP context menu options on Teiid tables should consider whether virtual model supports update.

by Ken Johnson (JIRA)

DTP context menu options on Teiid tables should consider whether virtual model supports update. ----------------------------------------------------------------------------------------------- Key: TEIIDDES-518 URL: https://jira.jboss.org/browse/TEIIDDES-518 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.0 Environment: Teiid Designer 7.0 + JBoss Dev Studio 3.0.1GA Teiid 7.1 Alpha on EAP 5.1 RHEL 6, OpenJDK 1.6 Reporter: Ken Johnson In DTP, Context menu for Table contains several options under Data->(Edit, Load, Extract, Sample Contents). For virtual tables, Extract and Sample Contents are fine. Edit and Load will attempt to write data. Thus a few issues: a) These options should be disabled if the table in question does not have Supports Update checked. b) These options should be tested when the table *does* have Update and Insert procedures defined. c) Tables in SYS schema should never be writable. When working with physical tables, all options should be available and work correctly. Cursory testing indicates this is the case - at least with a MySQL data source underlying the model. -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-268) "Create Web Service" wizard on a virtual procedure produces invalid SQL in transformation

by Debbie Steigner (JIRA)

"Create Web Service" wizard on a virtual procedure produces invalid SQL in transformation ----------------------------------------------------------------------------------------- Key: TEIIDDES-268 URL: https://jira.jboss.org/jira/browse/TEIIDDES-268 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.0 Reporter: Debbie Steigner Fix For: 7.0 If you use our "Create Web Service" wizard on a virtual procedure the SQL transformation for the Output View is invalid for the current product. For example, our wizard produced: SELECT * FROM (EXEC TwoStepsFeatureTable.TwoSteps(left_node = left_node)) AS TwoSteps so it errors on left_node: Resolver Error: Symbol left_node is specified with an unknown group context The transformation should be procedural relational instead: SELECT * FROM TwoStepsFeatureTable.TwoSteps -- 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

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-210) Add implicit conversion of NULL to correct datatype in transformation validator

by Marc Shirley (JIRA)

Add implicit conversion of NULL to correct datatype in transformation validator ------------------------------------------------------------------------------- Key: TEIIDDES-210 URL: https://jira.jboss.org/jira/browse/TEIIDDES-210 Project: Teiid Designer Issue Type: Feature Request Components: Transformations, Validation Affects Versions: 6.0.0, 6.1.0 Reporter: Marc Shirley When using NULL value as a column (ie, NULL as columnName), it is only implicitly converted to a string. When trying to use the NULL as a column of type date, integer, float, etc., the validator throws a warning that the transformation is not valid. If you wrap the NULL in a convert to the correct column datatype (ie, "convert(NULL,date)"), the transformation can be validated successfully. -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-188) Database Schema not used in sql query

by Ben Truitt (JIRA)

Database Schema not used in sql query ------------------------------------- Key: TEIIDDES-188 URL: https://jira.jboss.org/jira/browse/TEIIDDES-188 Project: Teiid Designer Issue Type: Bug Environment: Ubuntu 9.x eclipse 3.4.2 teiid_designer_6.0.0.v20090427_SNAPSHOT Postgresql 8.2 postgresql-8.3-604.jdbc4.jar Reporter: Ben Truitt It looks like the database schema specified in the XMI file for the model is not being used when generating the SQL query to preview data from the model. I'm attaching my model XMI file. Note the schema is named "rollback". However, the SQL query generated does not include the schema name, instead it only includes the table name. -- 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

13 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-304) External metadata needs to be marked as scalar groups where appropriate

by Van Halbert (JIRA)

External metadata needs to be marked as scalar groups where appropriate ----------------------------------------------------------------------- Key: TEIIDDES-304 URL: https://jira.jboss.org/jira/browse/TEIIDDES-304 Project: Teiid Designer Issue Type: Task Components: Modeling Reporter: Van Halbert Priority: Minor Fix For: 7.1 External temp metadata supplied by the designer should be marked as coming from a scalar group for INPUT, CHANGING, and VARIABLES groups. -- 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

13 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-217) JDBC Import Error from MySQL with BIT datatypes

by Mark Drilling (JIRA)

JDBC Import Error from MySQL with BIT datatypes ----------------------------------------------- Key: TEIIDDES-217 URL: https://jira.jboss.org/jira/browse/TEIIDDES-217 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0, 6.1.0, 6.2.0, Future Reporter: Mark Drilling Assignee: Barry LaFond Priority: Minor JDBC import from a MySQL database having columns of BIT datatype fails. The import succeeds, but attempts to re-open the generated relational model fail. Further inspection of the .xmi shows that an incorrect 'defaultValue' for the column has been written to the xmi model file. -- 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

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-178) Error initializing mirrors for: jar:file:C:\Documents and Settings\admindv.SLNTQM13\Desktop\teiid_designer_6.0.0.v20090430.zip!/

by Warren Gibson (JIRA)

Error initializing mirrors for: jar:file:C:\Documents and Settings\admindv.SLNTQM13\Desktop\teiid_designer_6.0.0.v20090430.zip!/ -------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-178 URL: https://jira.jboss.org/jira/browse/TEIIDDES-178 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0 Environment: Windows XP Client Reporter: Warren Gibson Priority: Minor I had downloaded Eclipse 3.4.1 and installed it as a fresh install. I got teiid_designer_6.0.0.v20090430 from SVN. The designer zip file was on my desktop. I took the normal steps to install designer. When it installed I got the following. This seems to happen with every install on the Windows client. Not sure if it is a defect or is related to the designer zip being on my desktop. Error initializing mirrors for: jar:file:C:\Documents and Settings\admindv.SLNTQM13\Desktop\teiid_designer_6.0.0.v20090430.zip!/ java.net.URISyntaxException: Relative path in absolute URI: jar://file:C:%5CDocuments%20and%20Settings%5Cadmindv.SLNTQM13%5CDesktop%5Cteiid_designer_6.0.0.v20090430.zip!/ at java.net.URI.checkPath(Unknown Source) at java.net.URI.<init>(Unknown Source) at org.eclipse.equinox.internal.p2.core.helpers.URLUtil.toURI(URLUtil.java:65) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorSelector.<init>(MirrorSelector.java:106) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getMirror(SimpleArtifactRepository.java:490) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:447) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:515) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:162) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:146) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:94) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:504) at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:64) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-167) Designer should modify workspace.properties file used by DQP to replace relative folder entries with absolute folders in the system temp folder

by Johnny Verhaeg (JIRA)

Designer should modify workspace.properties file used by DQP to replace relative folder entries with absolute folders in the system temp folder ----------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-167 URL: https://jira.jboss.org/jira/browse/TEIIDDES-167 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Affects Versions: 6.0.0 Reporter: Johnny Verhaeg The folders in the workspace.properties file in the org.teiid.dqp project are currently being created in the Eclipse installation folder at runtime; i.e., they are not even relative to the workspace. This file is read directly by Teiid Embedded, so to correct this issue, we should load the properties, modify the folder entries to be absolute entries within the system temp folder, and save them before handing the URL of the file to Teiid Embedded in dqp.ui.QueryClient.buildConnectionURL(). -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-428) Give the Designer's .log file a real name

by Paul Nittel (JIRA)

Give the Designer's .log file a real name ----------------------------------------- Key: TEIIDDES-428 URL: https://jira.jboss.org/jira/browse/TEIIDDES-428 Project: Teiid Designer Issue Type: Feature Request Components: Housekeeping Affects Versions: 7.0 Environment: All Reporter: Paul Nittel (I called this a Feature since it's been this way for years and we've not recorded it as a defect before.) The MetaMatrix and Teiid Designers have always created a .log file in the .metadata directory. The name is not easy to find and is a nuisance to use (for example, when attaching the log file to an email message). Please incorporate a "real" name, like "designer.log". -- 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

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-242) Salesforce Importer model update does not correctly update extension metadata.

by John Doyle (JIRA)

Salesforce Importer model update does not correctly update extension metadata. ------------------------------------------------------------------------------ Key: TEIIDDES-242 URL: https://jira.jboss.org/jira/browse/TEIIDDES-242 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0, 6.1.0, 6.2.0 Reporter: John Doyle Assignee: John Doyle Fix For: Future -- 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

13 years, 10 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2010