[
https://issues.apache.org/jira/browse/JDO-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528495
]
Ilan Kirsh commented on JDO-529:
--------------------------------
Thanks, the patch looks good.
By the way, I read that such a DISTINCT / ORDER BY combination causes an error
in Oracle, where MySQL chooses the first (arbitrary) personId for sort. Adding
the order expression to the SELECT is a probably another (third) dialect.
> ChangeQuery - DISTINCT is expected even though it is not specified
> ------------------------------------------------------------------
>
> Key: JDO-529
> URL: https://issues.apache.org/jira/browse/JDO-529
> Project: JDO
> Issue Type: Test
> Components: tck2
> Reporter: Ilan Kirsh
> Attachments: jdo-529.patch
>
>
> Test org.apache.jdo.tck.query.api.ChangeQuery expects 3 result objects:
> List expectedResult = Arrays.asList(new Object[] {
> new FullName("emp1First", "emp1Last"),
> new FullName("emp2First", "emp2Last"),
> new FullName("emp5First", "emp5Last")});
> But actually there should be 4 result objects:
> List expectedResult = Arrays.asList(new Object[] {
> new FullName("emp1First", "emp1Last"),
> new FullName("emp2First", "emp2Last"),
> new FullName("emp2First", "emp2Last"),
> new FullName("emp5First", "emp5Last")});
> because the result is not specified as DISTINCT.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
