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) <[EMAIL PROTECTED]> 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. > >
