Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <4811173.1155251654307.JavaMail.jira@brutus>
Date: Thu, 10 Aug 2006 16:14:14 -0700 (PDT)
From: "Craig Russell (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Updated: (JDO-404) GetFetchPlan - Is it really forbidden to
 load extra fields?
In-Reply-To: <6996217.1155111553821.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JDO-404?page=all ]

Craig Russell updated JDO-404:
------------------------------

    Fix Version/s: JDO 2 maintenance release 1

> 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
>             Fix For: JDO 2 maintenance release 1
>
>
> 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