From dev-return-8239-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Sun May 25 02:42:21 2008 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 15258 invoked from network); 25 May 2008 02:42:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 May 2008 02:42:21 -0000 Received: (qmail 49122 invoked by uid 500); 25 May 2008 02:42:22 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 49098 invoked by uid 500); 25 May 2008 02:42:22 -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 49087 invoked by uid 99); 25 May 2008 02:42:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 May 2008 19:42:22 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 May 2008 02:41:36 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 362D7234C124 for ; Sat, 24 May 2008 19:41:58 -0700 (PDT) Message-ID: <1508509574.1211683318220.JavaMail.jira@brutus> Date: Sat, 24 May 2008 19:41:58 -0700 (PDT) From: "Patrick Linskey (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Updated: (OPENJPA-407) Cache SQL (or closer precursors to SQL) more aggressively In-Reply-To: <26454308.1192643510624.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/OPENJPA-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-407: ------------------------------------ Fix Version/s: (was: 1.1.0) 1.1.1 > Cache SQL (or closer precursors to SQL) more aggressively > --------------------------------------------------------- > > Key: OPENJPA-407 > URL: https://issues.apache.org/jira/browse/OPENJPA-407 > Project: OpenJPA > Issue Type: Improvement > Components: jdbc, kernel, query, sql > Affects Versions: 0.9.0, 0.9.6, 0.9.7, 1.0.0 > Reporter: Patrick Linskey > Fix For: 1.1.1 > > Attachments: findBy.patch, OPENJPA-407.patch, OPENJPA-407.patch, OPENJPA-407.patch, OPENJPA-407.patch, QuerySQLCache.doc > > > When data is not available in the data cache, OpenJPA dynamically creates SQL to look up the requested data. OpenJPA should more aggressively cache this SQL to accelerate pathways from a cache miss to the database. > The generated SQL takes a number of factors into account, including the requested records, transaction status, currently-loaded data, and the current fetch configuration. Any caching would need to account for these factors as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.