Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] Difference between cache-usage and maintain-cache query hints?

Read-only queries provide some optimizations related to some work we do for change detection. The features are compatible.

Laird Nelson wrote:
On Thu, Mar 17, 2011 at 10:18 AM, Tom Ware <tom.ware@xxxxxxxxxx <mailto:tom.ware@xxxxxxxxxx>> wrote:

    https://bugs.eclipse.org/bugs/show_bug.cgi?id=340309


I'm going to risk bothering you one last time.  :-)

So eclipselink.query-results-cache makes sense to me now, and is clearly the go-to hint I've been needing for quite some time.

How does this differ from read only queries (http://wiki.eclipse.org/Optimizing_the_EclipseLink_Application_%28ELUG%29#How_to_Use_Read-Only_Queries_for_Optimization)? Can I use these two query hints (eclipselink.read-only, if I recall) together? My sense is that read-only doesn't waste time doing the usual JPA entity stuff--change tracking, etc. and so it looks like I could use these two together for any "picklist" functionality.

L


------------------------------------------------------------------------

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users


Back to the top