Just to check - the hint can only be added to named
? not those built on the fly (which of course we are doing are
best to avoid :)
On 09/03/2012 13:45, Tom Ware wrote:
There
is no setting to do this universally for a whole persistence
unit. It should be possible to do this using EclipseLink-native
API in a SessionCustomizer by iterating through the queries
defined in the query manager and calling the required native API
to set it up. The timeouts could be set in the same code.
The reason there is no universal setting is that it is not clear
that this would be desirable in most use-cases. EclipseLink
already has a cache that provides quite a bit of performance boost
and the query results cache is intended to provide an additional
performance boost for selected queries. Using the query cache
requires an understanding about the degree to which results may be
stale when they come back.
-Tom
On 09/03/2012 8:16 AM, Tim Martin wrote:
Hi - anyone know if there is a valid
property to use in the persistence.xml to
cache all query results by name and parameter values.
So rather than putting a hint on the queries we can do something
like
<property name="eclipselink.query-results-cache"
value="true"/>
I've come across it searching in google - but not come across
anything defintive...
If so - how would we configure expiration of the cache ?
something simple like
expire everything every x minutes would do to start with..
Thanks
Tim
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
|