openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <>
Subject [jira] Resolved: (OPENJPA-407) Cache SQL (or closer precursors to SQL) more aggressively
Date Tue, 15 Jul 2008 19:37:31 GMT


Kevin Sutter resolved OPENJPA-407.

       Resolution: Fixed
    Fix Version/s:     (was: 1.1.1)
         Assignee: Fay Wang

I'm marking this Issue as Resolved for trunk (1.2.0).  Version 1.1.1 is still listed as a
potential Fix Version, but I'll leave that up to somebody else to see if it applies or if
they want it.

Additional sql generation optimizations or caching should be done via new related Issues.


> 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, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.1.0, 1.1.1
>            Reporter: Patrick Linskey
>            Assignee: Fay Wang
>             Fix For: 1.2.0
>         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.

View raw message