Yes, this is correct. Of course use LOCAL_CACHE only when you think it
is appropriate (i.e. the data doesn't change within a single user
session lifespan).
Also there's new pluggable 3.0 API that would allow you to control
expiration of the query cache. This should be considered advanced AP
Hi Andrus,
Thanks for the advice. To do this I presume I need to have Level 2 (local
VM) caching enabled, and then set caching policy as appropriate for the
query:
// For most of the queries
QueryMetadata.LOCAL_CACHE
// For cached lookup data
QueryMetadata.SHARED_CACHE
regards Malcolm Edgar
O
