Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4EE0510961 for ; Tue, 29 Oct 2013 16:26:27 +0000 (UTC) Received: (qmail 65427 invoked by uid 500); 29 Oct 2013 16:25:15 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 65155 invoked by uid 500); 29 Oct 2013 16:24:59 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 64764 invoked by uid 99); 29 Oct 2013 16:24:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2013 16:24:34 +0000 Date: Tue, 29 Oct 2013 16:24:34 +0000 (UTC) From: "Jody Grassel (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (OPENJPA-2414) FinderCache does not consider active Fetch Groups/FetchPlan added Fields MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jody Grassel resolved OPENJPA-2414. ----------------------------------- Resolution: Fixed > FinderCache does not consider active Fetch Groups/FetchPlan added Fields > ------------------------------------------------------------------------ > > Key: OPENJPA-2414 > URL: https://issues.apache.org/jira/browse/OPENJPA-2414 > Project: OpenJPA > Issue Type: Bug > Components: kernel > Affects Versions: 2.2.3, 2.3.0 > Reporter: Jody Grassel > Assignee: Jody Grassel > Fix For: 2.1.2, 2.2.1.1, 2.2.3, 2.3.0 > > > The FinderCache retains a Map, associating a ClassMapping with a FinderQuery. However, this cache does not factor in the characteristics of the FetchPlan that was active when a mapping is created, nor does it factor them to determine if a cache hit is appropriate. This causes the find() operation to perform the same SQL as the first time it was executed, regardless of changes to the active FetchPlan afterwards. -- This message was sent by Atlassian JIRA (v6.1#6144)