Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 27272 invoked from network); 2 Oct 2006 23:51:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Oct 2006 23:51:25 -0000 Received: (qmail 27376 invoked by uid 500); 2 Oct 2006 23:51:24 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 27230 invoked by uid 99); 2 Oct 2006 23:51:23 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Oct 2006 16:51:23 -0700 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=HTML_MESSAGE Received: from [212.150.49.174] ([212.150.49.174:27803] helo=mtaout4.barak.net.il) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 0D/90-29668-6F5A1254 for ; Mon, 02 Oct 2006 16:51:20 -0700 Received: from ILANC ([89.0.159.175]) by mtaout4.barak.net.il (Sun Java System Messaging Server 6.2-6.02 (built Apr 25 2006)) with ESMTPA id <0J6J003NT8X5MH80@mtaout4.barak.net.il> for jdo-dev@db.apache.org; Tue, 03 Oct 2006 01:51:06 +0200 (IST) Date: Tue, 03 Oct 2006 01:52:56 +0200 From: Ilan Kirsh Subject: CHALLENGE org.apache.jdo.tck.query.api.GetFetchPlan To: jdo-dev@db.apache.org Reply-to: Ilan Kirsh Message-id: <019301c6e67d$f8317890$0500000a@ILANC> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Mailer: Microsoft Outlook Express 6.00.2900.2869 Content-type: multipart/alternative; boundary="----=_NextPart_000_018E_01C6E68E.A58D8E60" X-Priority: 3 X-MSMail-priority: Normal X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_NextPart_000_018E_01C6E68E.A58D8E60 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Hi, This is also known as JDO-404 in the issue tracker. 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):=20 "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... Regards, Ilan Kirsh ObjectDB Software http://www.objectdb.com ------=_NextPart_000_018E_01C6E68E.A58D8E60--