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

JDO

GetFetchPlan - Is it really forbidden to load extra fields?

Created: 09/Aug/06 08:18 AM Updated: 05/Oct/06 03:19 PM

Return to search

Component/s:

tck2

Affects Version/s:

JDO 2 final

Fix Version/s:

JDO 2 maintenance release 1, JDO 2 TCK challenge fixes

Time Tracking:

Not Specified

File Attachments:

	File Name	Date Attached	Attached By	Size
	JDO-404.patch	2006-10-04 09:28 PM	Michael Bouschen	4 kB

Resolution Date:

05/Oct/06 03:19 PM

Description

« Hide

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

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Craig Russell made changes - 10/Aug/06 11:12 PM

Field	Original Value	New Value
Fix Version/s		JDO 2 maintenance release 1 [ 12310923 ]

Craig Russell made changes - 10/Aug/06 11:28 PM

Assignee

Craig Russell [ clr ]

Craig Russell made changes - 04/Oct/06 08:58 PM

Assignee

Craig Russell [ clr ]

Michael Bouschen [ mbo ]

Craig Russell made changes - 04/Oct/06 08:59 PM

Fix Version/s

JDO 2.0 TCK challenge fixes [ 12312093 ]

Michael Bouschen made changes - 04/Oct/06 09:28 PM

Attachment

JDO-404.patch [ 12342290 ]

Michael Bouschen made changes - 05/Oct/06 03:19 PM

Status	Open [ 1 ]	Resolved [ 5 ]
Resolution		Fixed [ 1 ]