Better cache mapping

[guilhermeblanco]

Currently, if you use a non-default cache support, like Redis, you're forced to map 3 instances for a single entity manager.
To simplify this support, and also make #65 and also remove the need of http://knpbundles.com/search?q=cache, we could use the 2.2 CacheBundle support ( symfony/symfony#3225 ) or simplify this by allowing our own cache:

doctrine:
    cache:
        apc: ~
    orm:
        // ...
        metadata_cache_driver: apc

This would also allow people to retrieve the cache drivers from service container.

[stof]

When I thought about this a while ago, @beberlei said that using separate cache instances for the different doctrine caches was a better idea. Implementing it would push people to go the other way by using the same cache for the metadata, the queries and the results

[guilhermeblanco]

@stof not really.
If you have a cluster, you may want to have a single connection.

Bu this does not prohibit people from having one per type. It'd just be a matter of implementing different cache connection (where I named the example as "apc").

So, this approach allows both, while the current support only allows multiple connections.

[intel352]

Not sure how much has changed since the last comment, but one of the cache definitions allows you to specify it's type as "service" and the id of the service. So if you reference the same service 3 times, doesn't that allow the same cache connection for each cache type?

[kimhemsoe]

Closing as not relevant anymore.