[JDO-404] GetFetchPlan - Is it really forbidden to load extra fields?

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JDO 2 final (2.0)
• Fix Version/s: JDO 2 maintenance release 1 (2.1), JDO TCK challenge fixes
• Component/s: tck
• Assignee: Michael Bouschen
• Reporter: Ilan Kirsh
• Created: 09/Aug/06 08:18
• Updated: 14/Jun/10 11:08
• Resolved: 05/Oct/06 15:19

Description

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...