openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OPENJPA-1151) Cache the current-time timestamp in AbstractQueryCache.onTypesChanged()
Date Tue, 15 Sep 2009 18:46:57 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Donald Woods resolved OPENJPA-1151.
-----------------------------------

    Resolution: Fixed

test failures on other dbs fixed by Fay with r815366 and r815369.

> Cache the current-time timestamp in AbstractQueryCache.onTypesChanged()
> -----------------------------------------------------------------------
>
>                 Key: OPENJPA-1151
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1151
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jdbc
>    Affects Versions: 1.3.0, 2.0.0
>            Reporter: Jody Grassel
>            Assignee: Donald Woods
>            Priority: Trivial
>             Fix For: 1.3.0, 2.0.0-M3
>
>         Attachments: OpenJPA-trunk-JIRA1151-tests.patch, OpenJPA-trunk-JIRA1151.patch
>
>
> AbstractQueryCache.java contains the following block:
>            for (Object o: changedTypes) {
>                 String name = ((Class) o).getName();
>                 if(!changedClasses.containsKey(name))
>                     changedClasses.put(name, 
>                         new Long(System.currentTimeMillis()));
>             }
> Suggesting caching the Long containing the entity type's last-modification timestamp
outside of the for-loop to improve performance and reduce memory usage.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message