Bug 352500

Description Sebastian 2011-07-19 15:17:38 EDT

from http://www.eclipse.org/forums/index.php?t=rview&goto=698571#msg_698571

Hi All,


I have a cached namedquery

Code: [Select all] [Show/ hide]

@NamedQuery(name = "CoverholderAgreement.all",
        query = "SELECT c FROM CoverholderAgreement c",
        hints = {
            @QueryHint(name = QueryHints. QUERY_RESULTS_CACHE, value=HintValues.TRUE)
        })



which speed up my code significantly... (so far so good)

in some part of the application I add and delete objects... doing that, the namedquery cache is not automatically refreshed so I need to refresh it by hand at every occation that I modify the DB:

Quote:


    utx.commit();
    ((JpaEntityManager)em.getDelegate()).getServerSession().getIdentityMapAccessor().clearQueryCache("CoverholderAgreement.all");



I do not like this option as it leads to generate new bugs... think about the case when I persist another object which by CASCADING persists a new CoverholderAgreement and I forget to refresh the namedquery cache... (this things hapends specially after some time or when future developers maintain the code and they are not aware of some cached namedquery)...

so just wondering if there is a better way for doing it ????

thanks !