[ 
https://issues.apache.org/jira/browse/JDO-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Bouschen updated JDO-568:
---------------------------------

    Attachment: JDO-568.patch

Good catch!

The purpose of this query is to generate a memory collection including all the 
employees and pass this as the candidate collection to the query test. I think 
we cannot use method executeJDOQuery for this purpose, because the method 
executes the query and compares the result against the expected result passed 
as a parameter. I propose to enclose the query execution in a tx begin/commit. 

Attached you find a patch for review (JDO-568.patch). It adds a helper method 
to the superclass that returns the list of all employees. 

> Add subquery support to JPOX
> ----------------------------
>
>                 Key: JDO-568
>                 URL: https://issues.apache.org/jira/browse/JDO-568
>             Project: JDO
>          Issue Type: Task
>          Components: tck2, tck2-legacy
>    Affects Versions: JDO 2 maintenance release 1
>            Reporter: Michael Bouschen
>            Assignee: Andy Jefferson
>             Fix For: JDO 2 maintenance release 1
>
>         Attachments: JDO-568.patch
>
>
> The subquery test cases currently fail, because JPOX does not yet support 
> subqueries:
>     [java] RUN CorrelatedSubqueries.testPositive           ERROR
>     [java] RUN CorrelatedSubqueriesWithParameters.testPositive     ERROR
>     [java] RUN MultipleCallsReplaceSubquery.testPositive           ERROR
>     [java] RUN NonCorrelatedSubqueries.testPositive        ERROR
>     [java] RUN NullCandidateCollectionExpression.testPositive      ERROR
>     [java] RUN NullSubqueryParameter.testPositive          ERROR
>     [java] RUN UnmodifiedSubqueryInstance.testPositive     ERROR 
> Here is the corresponding JPOX JIRA: 
> http://www.jpox.org/servlet/jira/browse/CORE-3207.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to