openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Bauer (JIRA)" <>
Subject [jira] Commented: (OPENJPA-407) Cache SQL (or closer precursors to SQL) more aggressively
Date Thu, 24 Apr 2008 19:15:22 GMT


Jeremy Bauer commented on OPENJPA-407:

Attaching the patch Kevin referred to in his previous post.  The patch contains code updates,
testcases, and OpenJPA documentation for a new QuerySQLCache property.  This property provides
configurable EMF-scope caching of select statements employed by the find operation.

Fay Wang (another OpenJPA contributor), in addition to making a large contribution to the
code, wrote the bulk of the extra documentation (QuerySQLCache.doc) to go along with this
patch.  It explains the performance issue and how it is addressed by this update.

The patch also contains a couple miscellanous updates (most notably a change in FetchConfigurationImpl
to eliminate hash queries for known values) that were flagged as target areas by a code profiler.

Please review the patch and post comments. 


> Cache SQL (or closer precursors to SQL) more aggressively
> ---------------------------------------------------------
>                 Key: OPENJPA-407
>                 URL:
>             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.0
>         Attachments: findBy.patch, OPENJPA-407.patch, OPENJPA-407.patch
> 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.

View raw message