From jdo-dev-return-7101-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org Fri Feb 01 19:05:35 2008 Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 19769 invoked from network); 1 Feb 2008 19:05:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Feb 2008 19:05:33 -0000 Received: (qmail 87572 invoked by uid 500); 1 Feb 2008 19:05:22 -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 87331 invoked by uid 99); 1 Feb 2008 19:05:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2008 11:05:21 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2008 19:05:02 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4BFD2714069 for ; Fri, 1 Feb 2008 11:05:09 -0800 (PST) Message-ID: <17236016.1201892709306.JavaMail.jira@brutus> Date: Fri, 1 Feb 2008 11:05:09 -0800 (PST) From: "Craig Russell (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Resolved: (JDO-489) Spec section 12.7.5: mention getFetchPlan() method of Extent interface In-Reply-To: <1447731.1179432256418.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JDO-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell resolved JDO-489. ------------------------------- Resolution: Fixed The spec as of 2008-02-15 reflects this change in 12.7.5: Fetch groups are activated using methods on the interface FetchPlan. PersistenceManager, Extent, and Query have getFetchPlan() methods. When a Query or Extent is created from a persistence manager, its fetch plan is initialized to the same settings as that of the persistence manager. A12.7.5-1 [Subsequent modifications of the Query or Extent fetch plan are localized (not reflected in the fetch plan of the persistence manager]). Similarly, subsequent modifications of the fetch plan of the persistence manager are not reflected in any existing Query or Extent. > Spec section 12.7.5: mention getFetchPlan() method of Extent interface > ---------------------------------------------------------------------- > > Key: JDO-489 > URL: https://issues.apache.org/jira/browse/JDO-489 > Project: JDO > Issue Type: Bug > Components: specification > Reporter: Michelle Caisse > Assignee: Craig Russell > Fix For: JDO 2 maintenance release 1 > > > Section 12.7.5 of the spec should mention Extent in the list of interfaces that have a getFetchPlan() method. Also should mention effect on Extent FetchPlan of modifying pm FetchPlan and Query FetchPlan (and vice versa). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.