[JBoss JIRA] (TEIID-2783) ModeShape query isn't retaining quotes defined for column in NIS
by Van Halbert (JIRA)
Van Halbert created TEIID-2783:
----------------------------------
Summary: ModeShape query isn't retaining quotes defined for column in NIS
Key: TEIID-2783
URL: https://issues.jboss.org/browse/TEIID-2783
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.4.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Issuing query:
SELECT jcr_name FROM nt_base AS children WHERE JCR_ISCHILDNODE(children.jcr_path, '/pathtoparent')
produces exception:
Caused by: javax.jcr.query.InvalidQueryException: The JCR-SQL2 query "SELECT g_0.jcr:name FROM "nt:base" AS g_0 WHERE ISCHILDNODE(g_0.jcr:path, '/pathtoparent')" is not well-formed: Expecting "FROM" but found ":" at line 1, column 15: SELECT g_0.jcr ===>> :name FROM "nt:base"
at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:146)
at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:101)
--
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, 4 months
[JBoss JIRA] (TEIID-2776) ArrayIndexOutOfBoundsException
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2776?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-2776:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1045204
> ArrayIndexOutOfBoundsException
> ------------------------------
>
> Key: TEIID-2776
> URL: https://issues.jboss.org/browse/TEIID-2776
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.5
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Priority: Critical
> Labels: exception, teiid
> Fix For: 8.6
>
>
> When executing the following query:
> insert into #tmp_labres
> select f.patientid as admissionid, f.variableid, f.sampledate, f.value, f.stringvalue, f.status
> from (
> select v.*, rank() over(partition by v.patientid,v.VariableID, v.sampledate order by v.SampleTime,v.resultno desc) as resultrank
> from #tmp_labrestimecast v
> ) f
> where f.resultrank = 1;
> I get and ArrayIndexOutOfBoundsException. In the logs it only says "11:31:44,537 ERROR [org.teiid.PROCESSOR] (Worker15031_QueryProcessorQueue278439) yfgMWpMOgQdg TEIID30019 Unexpected exception for request yfgMWpMOgQdg.43: java.lang.ArrayIndexOutOfBoundsException
> "
> A few log entries before this I find a stack trace for an ArrayIndexOutOfBoundsException. Since I have executed this query multiple times I think it's a stack trace for the same query. I suppose this has something to do with the rank function. A normal select on #tmp_labrestimecast works without a problem.
> 16:25:39,765 ERROR [org.teiid.PROCESSOR] (Worker13352_QueryProcessorQueue214542) 90UM8pskkEDH TEIID30019 Unexpected exception for request 90UM8pskkEDH.255: java.lang.ArrayIndexOutOfBoundsException: 1
> at java.util.Arrays$ArrayList.get(Arrays.java:2866) [rt.jar:1.7.0_25]
> at org.teiid.query.processor.relational.WindowFunctionProjectNode.nextBatchDirect(WindowFunctionProjectNode.java:270) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:104) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.ProjectIntoNode.nextBatchDirect(ProjectIntoNode.java:138) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:155) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:435) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:320) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:248) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
--
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, 4 months
[JBoss JIRA] (TEIID-2776) ArrayIndexOutOfBoundsException
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2776?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2776:
---------------------------------------
Should be targeted for 8.4.2 as well.
> ArrayIndexOutOfBoundsException
> ------------------------------
>
> Key: TEIID-2776
> URL: https://issues.jboss.org/browse/TEIID-2776
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.5
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Priority: Critical
> Labels: exception, teiid
> Fix For: 8.6
>
>
> When executing the following query:
> insert into #tmp_labres
> select f.patientid as admissionid, f.variableid, f.sampledate, f.value, f.stringvalue, f.status
> from (
> select v.*, rank() over(partition by v.patientid,v.VariableID, v.sampledate order by v.SampleTime,v.resultno desc) as resultrank
> from #tmp_labrestimecast v
> ) f
> where f.resultrank = 1;
> I get and ArrayIndexOutOfBoundsException. In the logs it only says "11:31:44,537 ERROR [org.teiid.PROCESSOR] (Worker15031_QueryProcessorQueue278439) yfgMWpMOgQdg TEIID30019 Unexpected exception for request yfgMWpMOgQdg.43: java.lang.ArrayIndexOutOfBoundsException
> "
> A few log entries before this I find a stack trace for an ArrayIndexOutOfBoundsException. Since I have executed this query multiple times I think it's a stack trace for the same query. I suppose this has something to do with the rank function. A normal select on #tmp_labrestimecast works without a problem.
> 16:25:39,765 ERROR [org.teiid.PROCESSOR] (Worker13352_QueryProcessorQueue214542) 90UM8pskkEDH TEIID30019 Unexpected exception for request 90UM8pskkEDH.255: java.lang.ArrayIndexOutOfBoundsException: 1
> at java.util.Arrays$ArrayList.get(Arrays.java:2866) [rt.jar:1.7.0_25]
> at org.teiid.query.processor.relational.WindowFunctionProjectNode.nextBatchDirect(WindowFunctionProjectNode.java:270) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:104) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.ProjectIntoNode.nextBatchDirect(ProjectIntoNode.java:138) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:155) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:435) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:320) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:248) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.5.0.Final.jar:8.5.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
--
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, 4 months
[JBoss JIRA] (TEIID-2781) Unable to update database table with composite keys using OData
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2781?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2781.
-----------------------------------
Resolution: Done
Changed to just toString and added validation to ensure that partial composite keys are not used. This should probably be queued up for 8.4.2.
> 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.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, 4 months
[JBoss JIRA] (TEIID-2781) Unable to update database table with composite keys using OData
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2781?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2781:
-------------------------------------
yes, that looks good. Thanks
> 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.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, 4 months
[JBoss JIRA] (TEIID-2781) Unable to update database table with composite keys using OData
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2781?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2781:
----------------------------------
Fix Version/s: 8.7
Ramesh, have a look at ODataSQLBuilder.buildEntityKeyCriteria change to make sure it matches your expectations.
> 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.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, 4 months
[JBoss JIRA] (TEIID-2781) Unable to update database table with composite keys using OData
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2781?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2781:
-------------------------------------
I do not think so, when EntityType is defined with composite id keys, then to access using the id, all of them need to present. Partial keys is not supported, otherwise user has choice to use $filter which becomes generic criteria. You are correct was not checking the validity of they in that code.
> 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
> 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, 4 months
[JBoss JIRA] (TEIID-2781) Unable to update database table with composite keys using OData
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2781?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2781:
---------------------------------------
I think there is an issue with the ODataSQLBuilder.buildEntityKeyCriteria logic then at least for the purposes of delete. The logic assumes that a single value means to use the first column of the primary key, but if odata4j does not validate the key (as it appears to do with delete) then that is not a valid assumption. Are there in cases where it's valid for the buildEntityKeyCriteria to lookup based upon a partial key?
> 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
> 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, 4 months
[JBoss JIRA] (TEIID-2781) Unable to update database table with composite keys using OData
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2781?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2781:
-------------------------------------
yes, composite keys should be always used with name value scope.
> 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
> 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, 4 months