Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of techhusky@gmail.com
 designates 66.249.90.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=RJ2rBe0qaxYOkugUURij7jRouRA4Wji098lXwCNNjiaGIiggXKzBqQvfsSYDmUMYJeBO9xuhvSyg1+SgsE0jLaymbrJbls3gnZ9JuPrHTm8olBvUdmTM65sOTqaf8ABoDvFGgZQ+Hk96bL1c4uQU6esA4JffbmyOELLqgWUhk+I=
Message-ID: <c4a1048f0805270808l59a3cd46h9ba87bb82d42bae1@mail.gmail.com>
Date: Tue, 27 May 2008 10:08:11 -0500
From: "Jeremy Bauer" <techhusky@gmail.com>
To: dev@openjpa.apache.org
Subject: Re: [jira] Updated: (OPENJPA-407) Cache SQL (or closer precursors to
 SQL) more aggressively
In-Reply-To: <1508509574.1211683318220.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <26454308.1192643510624.JavaMail.jira@brutus>
	 <1508509574.1211683318220.JavaMail.jira@brutus>

Hi Patrick.

The 1.1.0 release notes currently list OPENJPA-407 as an improvement,
but I see you've just changed the fix version to 1.1.1 (and there is
no commit for the 1.1.0 release).  It appears that the release note
tooling may rely only on the fix version when generating the doc?  I
am unable to bring up the JIRA history so I can't determine if/when
the fix version was last modified.

-Jeremy

On 5/24/08, Patrick Linskey (JIRA) <jira@apache.org> wrote:
>
>     [ 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.
>
>