Ah that's right. A local query cache is created that belongs to this
context only.
Not sure if we need to document it though. This is the internal
details that are likely to change between releases.
Andrus
On May 28, 2010, at 10:17 AM, Gary Jarrel wrote:
On Fri, May 28, 2010 at 4:43 PM, A
On Fri, May 28, 2010 at 4:43 PM, Andrus Adamchik wrote:
>
>> it seems that domain.getQueryCache().size() is returning 1
>>
>> assertEquals(1, ((DataContext)
>> getDataContext()).getParentDataDomain().getQueryCache().size());
>> assertEquals(1, ((DataContext) getDataContext()).getQueryCache().size
On May 28, 2010, at 9:39 AM, Gary Jarrel wrote:
So does this mean that for query caching to work I have to specify the
cache group and cache strategy and that the modeler settings only
apply to Object cache?
Yes. Essentially at the query level you decide whether you want it
cached or not. S
On Fri, May 28, 2010 at 4:28 PM, Andrus Adamchik wrote:
>
> On May 28, 2010, at 9:20 AM, Gary Jarrel wrote:
>
>> I would expect that the the second query q2 would not execute any SQL
>> however the QueryLogger logs the second select statement.
>
> The second query has no cache group or cache strat
On May 28, 2010, at 9:20 AM, Gary Jarrel wrote:
I would expect that the the second query q2 would not execute any SQL
however the QueryLogger logs the second select statement.
The second query has no cache group or cache strategy in your example,
so it is not using caching.
Also the asse
On Fri, May 28, 2010 at 4:20 PM, Gary Jarrel wrote:
> SelectQuery q = new SelectQuery(Admin.class);
> q.setCacheGroups("testGroup");
> q.setCacheStrategy(QueryCacheStrategy.SHARED_CACHE);
>
> List result = getDataContext().performQuery(q);
> assertEquals(2, result.size());
Further
Hi All
I'm still trying to wrap my head around the Cayenne caching system,
(maybe Friday afternoon isn't doing me any good)
I have a test case as follows:
public void testBasicSelectQueryWithoutDaoWithCache() {
initCache();
assertEquals(0, getDataContext().getQueryCache().size());
S
