db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JDO-410) AggregateResult queries non-existent Employee.manager.salary field
Date Thu, 14 Sep 2006 21:38:25 GMT
     [ http://issues.apache.org/jira/browse/JDO-410?page=all ]

Michael Bouschen resolved JDO-410.

    Resolution: Fixed

Checked in the patch (see revision 443484).

> AggregateResult queries non-existent Employee.manager.salary field
> ------------------------------------------------------------------
>                 Key: JDO-410
>                 URL: http://issues.apache.org/jira/browse/JDO-410
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Marc Prud'hommeaux
>         Assigned To: Michael Bouschen
>             Fix For: JDO 2 maintenance release 1
>         Attachments: JDO-410.patch
> In 6 different places in the AggregateResult test, a query is issued against FullTimeEmployee
and returns an aggregate on "manager.salary". However, the "manager" field is of type Employee,
and the "salary" field is only defined in the FullTimeEmployee subclass of Employee, thus
rendering the aggregate statement invalid.
> The solution is to replace all instances of "manager.salary" with a clause that casts
"manager" down to "FullTimeEmployee". E.g.: "(((FullTimeEmployee)manager).salary)"

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message