[JBoss JIRA] (TEIID-2781) Unable to update database table with composite keys using OData
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2781?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-2781:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1044746|https://bugzilla.redhat.com/show_bug.cgi?id=1044746] from NEW to MODIFIED
> Unable to update database table with composite keys using OData
> ---------------------------------------------------------------
>
> Key: TEIID-2781
> URL: https://issues.jboss.org/browse/TEIID-2781
> Project: Teiid
> Issue Type: Bug
> Components: SOAP Services
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.7
>
> Attachments: odataerror.txt, post-screen-shot.png, Shell00990083.tar
>
>
> Using Postgres db, and created a table with composite keys.
> CREATE TABLE composite_key
> (
> ou_id character varying(3) NOT NULL,
> product_name character varying(15) NOT NULL,
> product_price numeric(10,2),
> CONSTRAINT composite_key_pkey PRIMARY KEY (ou_id, product_name)
> )
> WITH (
> OIDS=FALSE
> );
> ALTER TABLE composite_key OWNER TO postgres;
> INSERT INTO composite_key VALUES ('1','1',1);
> INSERT INTO composite_key VALUES ('1','2',1.20);
> INSERT INTO composite_key VALUES ('2','1',2.10);
> Deploy the VDB and use SOAP UI to do PUT (aka SQL UPDATE) generates attached odataerror.txt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (TEIID-2779) Configurable CommonTableExpression support for DB2
by Andriy Rokhmanov (JIRA)
[ https://issues.jboss.org/browse/TEIID-2779?page=com.atlassian.jira.plugin... ]
Andriy Rokhmanov commented on TEIID-2779:
-----------------------------------------
We did additional research, seems DB2 for z/OS V9.1 in Conversion Mode does not support ORDER BY inside CTE either. Error message we are getting: "ATTEMPT TO USE NEW FUNCTION BEFORE NEW FUNCTION MODE. SQLCODE=-4700, SQLSTATE=56038, DRIVER=4.12.55"
The approach proposed on 20/Dec/13 3:46 PM does not help either. This makes CTE approach for DB2 on z/OS a very difficult to keep for certain DB2 versions.
> Configurable CommonTableExpression support for DB2
> --------------------------------------------------
>
> Key: TEIID-2779
> URL: https://issues.jboss.org/browse/TEIID-2779
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Affects Versions: 8.5
> Reporter: Andriy Rokhmanov
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> The LIMIT clause (FETCH FIRST...) inside CTE (WITH...) is not supported on pre-V9 versions of DB2 on z/OS, or new versions of DB2 running in Compatibility Mode.
> The CTE support in DB2 translator should be configurable.
> See more information:
> https://community.jboss.org/thread/235503
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-2786:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1048948 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1046501)
> ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-2786
> URL: https://issues.jboss.org/browse/TEIID-2786
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 7.7
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 8.7
>
>
> When trying to use the Teiid Designer feature of importing using a Teiid Connection fails when the connection is to ModeShape. The following exception:
> 08:33:44,914 ERROR [stderr] (teiid-async-threads - 2) java.sql.SQLFeatureNotSupportedException
> 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.modeshape.jdbc.JcrMetaData.getTypeInfo(JcrMetaData.java:1656)
> 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:107)
> 08:33:44,915 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml")
> 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:280)
> 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:62)
> 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61)
> 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$6.run(VDBService.java:397)
> 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$7.run(VDBService.java:444)
> 08:33:44,918 ERROR [stderr] (teiid-async-threads - 2) at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
> My guess is the local modeshape jdbc driver hasn't been fully vetted in this area, as the remote JDBC version has been the one used when using the Modeshape eclipse plugin for importing the metadata.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months