[
https://issues.apache.org/jira/browse/JDO-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562899#action_12562899
]
Andy Jefferson commented on JDO-568:
------------------------------------
I'd suggest, after looking at the data as I interpret it, that the expectations
are wrong.
In "dept2" we have emp7, emp8, emp9, emp10. Only emp8 and emp9 have a manager
set so are the only ones considered in the average ... hence why emp9 is coming
through. Or is this a complete misinterpretation of that JDOQL subquery?
> 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.
