17. CachingΒΆ

A Doctrine\DBAL\Statement can automatically cache result sets.

For this to work an instance of Doctrine\Common\Cache\Cache must be provided. This can be set on the configuration object (optionally it can also be passed at query time):

$cache = new \Doctrine\Common\Cache\ArrayCache();
$config = $conn->getConfiguration();

To get the result set of a query cached it is necessary to pass a Doctrine\DBAL\Cache\QueryCacheProfile instance to the executeQuery or executeCacheQuery instance. The difference between these two methods is that the former does not require this instance, while the later has this instance as a required parameter:

$stmt = $conn->executeQuery($query, $params, $types, new QueryCacheProfile(0, "some key"));
$stmt = $conn->executeCacheQuery($query, $params, $types, new QueryCacheProfile(0, "some key"));

It is also possible to pass in a the Doctrine\Common\Cache\Cache instance into the constructor of Doctrine\DBAL\Cache\QueryCacheProfile in which case it overrides the default cache instance:

$cache = new \Doctrine\Common\Cache\FilesystemCache(__DIR__);
new QueryCacheProfile(0, "some key", $cache);

In order for the data to actually be cached its necessary to ensure that the entire result set is read (easiest way to ensure this is to use fetchAll) and the statement object is closed:

$stmt = $conn->executeCacheQuery($query, $params, $types, new QueryCacheProfile(0, "some key"));
$data = $stmt->fetchAll();
$stmt->closeCursor(); // at this point the result is cached


When using the cache layer not all fetch modes are supported. See the code of the ResultCacheStatement for details.

Project Versions

Previous topic

16. Portability

Next topic

18. Known Vendor Issues

This Page

Fork me on GitHub