| Michael Watzek (JIRA) 2005-11-25, 7:45 am |
| [ http://issues.apache.org/jira/browse/JDO-216?page=all ]
Michael Watzek resolved JDO-216:
--------------------------------
Resolution: Fixed
The attached patch has been checked in including the comments above (Revisiov 345514).
> Result handling in class QueryTest must be capable to consider return types of java.lang.Object
> -----------------------------------------------------------------------------------------------
>
> Key: JDO-216
> URL: http://issues.apache.org/jira/browse/JDO-216
> Project: JDO
> Type: Bug
> Components: tck20
> Reporter: Michael Watzek
> Assignee: Michael Watzek
> Attachments: JDO-216.patch
>
> The current result handling in class QueryTest cannot consider return types of type java.lang.Object. Unique queries and queries using aggregates in the select expression (single exression, no group by) return objects rather than collections. The resul
t handling must reflect this fact. As a consequence, the expected result in query test cases must be capable to consider a single object also.
> Currently, the expected result is declared as an object array in JDO2 query test classes. Method QueryTest.execute takes an object array as the expected result and an additional flag (unique) indicating if the query returns a single result. The unqiue p
arameter is calculated by methods in QueryTest executing query element holders. This is inadequate because the query element holder does not encapsulate the information of aggregates in single result expressions.
> We propose to adapt the signature and the implementation of method QueryTest.execute: The expected result should be of type java.lang.Object and the unique parameter should be removed. Thus, the unique information can be calculated inside the method.
> JDO2 query test classes in package query.api call method QueryTest.execute directly. These test cases must be adapted wrt the expected result: The expected result must be of the exact type which the query returns at runtime.
> Other test cases which do not call method QueryTest.execute directly may be adapted wrt the expected result as part of a separate issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|