Doctrine_manual-1-2-en

Chapter 23: Caching 326
// ...
$manager->setAttribute(Doctrine_Core::ATTR_RESULT_CACHE_LIFESPAN, 3600);
Now as we have set a cache driver for use we can make a DQL query use it by calling the
useResultCache() method:
Fetch blog post titles and the number of comments:
Listing
23-11
$q = Doctrine_Query::create()
->select('b.title, COUNT(c.id) count')
->from('BlogPost b')
->leftJoin('b.Comments c')
->limit(10)
->useResultCache(true);
$blogPosts = $q->execute();
Fine Tuning
In the previous chapter we used global caching attributes. These attributes can be overriden
at the query level. You can override the cache driver by calling useCache() and pass it an
instance of a valid Doctrine cache driver.
Listing
23-12
$q = Doctrine_Query::create()
->useResultCache(new Doctrine_Cache_Apc());
Also you can override the lifespan attribute by calling setResultCacheLifeSpan():
Listing
23-13
$q = Doctrine_Query::create()
->setResultCacheLifeSpan(60 * 30);
Conclusion
Using the caching feature of Doctrine is highly recommended in both development and
production environments. There are no adverse affects to using it and it will only help the
performance of your application.
The caching feature is the second to last feature we will discuss in this book before wrapping
things up by discussing things like the technologies used (page 368) in Doctrine, coding
standards (page 381) and unit testing (page 356). Lets move on to discuss the last feature of
Doctrine, Migrations (page 327).
----------------- Brought to you by