[
https://issues.apache.org/jira/browse/JDO-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Russell resolved JDO-473.
-------------------------------
Resolution: Fixed
The change to the spec was made with the version dated 2007-09-28.
> Retrieve/Refresh(obj,useFetchGroup) uses the fetch group fields. It would be
> nice if it applied the whole fetch plan contract
> Retrieve/Refresh(obj,useFetchPlan)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JDO-473
> URL: https://issues.apache.org/jira/browse/JDO-473
> Project: JDO
> Issue Type: Wish
> Components: specification
> Affects Versions: JDO 2 final
> Reporter: Erik Bengtson
> Assignee: Craig Russell
> Fix For: JDO 2 maintenance release 1
>
>
> The current Retrieve/Refresh(obj,useFetchGroup), useFetchGroup argument when
> set to true determines which fields from the fetch group should be loaded.
> It would be more consistent with makeTransient/detach and powerful if it
> would use the fetch plan instead Retrieve/Refresh(obj,useFetchPlan)
> § JDO 2 Spec 12.6.7 (makeTransient)
> "If the useFetchPlan parameter is true, the current FetchPlan, including
> MaxFetch-
> Depth, DETACH_LOAD_FIELDS, and DETACH_UNLOAD_FIELDS, is applied to the pc or
> pcs parameter instance(s) to load fields and instances from the datastore.
> Refers to:
> § JDO 2 Spec 12.6.1 (refresh/retried)
> § JDO 2 Spec 12.6.7 (makeTransient)
> § JDO 2 Spec 12.6.8 (detach)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
