[
https://issues.apache.org/jira/browse/JDO-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bouschen updated JDO-529:
---------------------------------
Attachment: JDO-529-addAscending.patch
I agree with what Andy said. We need to add the keyword ASCENDING such that the
ordering constraint becomes: firstname ASCENDING, lastname ASCENDING
Attached you find a patch (JDO-529-addAscending.patch) that adds the keyword
ASCENDING.
> 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
> Assignee: Craig Russell
> Fix For: JDO 2 maintenance release 1
>
> Attachments: JDO-529-addAscending.patch, 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.
