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-404) GetFetchPlan - Is it really forbidden to load extra fields?
Date Thu, 05 Oct 2006 15:21:20 GMT
     [ http://issues.apache.org/jira/browse/JDO-404?page=all ]

Michael Bouschen resolved JDO-404.

    Resolution: Fixed

Checked in the patch (see revision 453265).

> GetFetchPlan - Is it really forbidden to load extra fields?
> -----------------------------------------------------------
>                 Key: JDO-404
>                 URL: http://issues.apache.org/jira/browse/JDO-404
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Ilan Kirsh
>         Assigned To: Michael Bouschen
>             Fix For: JDO 2 maintenance release 1, JDO 2.0 TCK challenge fixes
>         Attachments: JDO-404.patch
> The tests in org.apache.jdo.tck.query.api.GetFetchPlan validate using jdoPostLoad that
some fields are not loaded in the query results. This doesn't make sense for implementations
in which avoiding loading value fields doesn't give any performance benefit, and I think that
it is also against the spec (page 127):
> "When an instance is loaded using getObjectById , a Query is executed, or an Extent is
iterated, the implementation may choose to use the active fetch groups to prefetch data."
- may choose and not must...

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