Deprecation of DoctrineCacheBundle

[alcaeus]

After evaluation, we have decided that we will not adapt this bundle for compatibility with Symfony 5. We will provide limited support while people continue to use it with Symfony 3.4 LTS and supported versions of Symfony 4, but we actively suggest people don't use this bundle anymore to configure caches from Symfony 5 onwards.

With Symfony 3.4, the Symfony Cache Component was introduced, along with a very simple way to configure it using FrameworkBundle. Unlike doctrine/cache, this component is compatible with the PHP-FIG cache standards (PSR-6 and PSR-16). With this in mind, symfony/cache is more interoperable than doctrine/cache, which was always specifically tailored to the needs of the Doctrine projects.

Last but not least, the cache bundle is no longer needed to configure caches for the DoctrineBundle: the current Symfony Flex recipe already configures symfony/cache adapters for ORM, and the new version of the bundle for ORM will support configuring a symfony/cache straight from the configuration. With all this in mind, there is no point allowing to configure doctrine/cache for anything other than it was originally intended to be used, which renders this bundle obsolete.

Please note that while we are preparing for DoctrineBundle to no longer depend on this bundle, we welcome feedback from the community on the deprecation of DoctrineCacheBundle. Please let us know if you are actively using this bundle to configure caches for usages outside of doctrine/orm. If you don't have a doctrine_cache node in your Symfony configuration, this deprecation will most likely not affect you at all. If you do, we'd appreciate your input.

[DavG]

Do you have a doc explaining how to make Doctrine works with Symfony Cache ?

Each times I tried, it was not working (cache:clear fails).

If I remember correctly, doctrine (I've forget what package exactly) was not compatible with PHP-FIG standard... so I always ended up by installing DoctrineCacheBundle...

[SenseException]

• Are we going to abandon the composer package at a specific time?
• To spread the information about the deprecation, we have to update the documentation. I also created a PR Create pull request template with deprecation info #157 to communicate this deprecation info to contributors.

[alcaeus]

@DavG:

Do you have a doc explaining how to make Doctrine works with Symfony Cache ?

Currently, you just create the cache pool you want to use, then create a DoctrineAdapter, as shown in the default recipe: https://github.com/symfony/recipes/blob/master/doctrine/doctrine-bundle/1.6/config/packages/prod/doctrine.yaml

With the new minor release of DoctrineBundle (to be released in May) you'll be able to specify a pool directly instead of having to wrap it in a DoctrineAdapter yourself.

Each times I tried, it was not working (cache:clear fails).

If I remember correctly, doctrine (I've forget what package exactly) was not compatible with PHP-FIG standard... so I always ended up by installing DoctrineCacheBundle...

That's correct - doctrine/cache does not implement PSR-6 or PSR-16, but this can be worked around (e.g. with the DoctrineAdapter class in symfony/cache)

@SenseException:

• Are we going to abandon the composer package at a specific time?

No decision on this yet since we'll fix bugs in the latest minor release for some time to come.

[dbu]

Are we going to abandon the composer package at a specific time?

No decision on this yet since we'll fix bugs in the latest minor release for some time to come.

i would not mark it as abandon right now, but maybe in summer? it will make people aware and make them move away. the README of this repo should clearly explain what is meant with the abandon and that for now its okay to keep using it in legacy projects. it might make sense to do a PR on the symfony/cache DoctrineAdaptor as well, to mark that one as deprecated (with an explanation) so that people notice.

[alcaeus]

it might make sense to do a PR on the symfony/cache DoctrineAdaptor as well, to mark that one as deprecated

Except that the DoctrineAdapter won't be deprecated: it's still necessary to allow using a PSR cache with any project expecting a doctrine/cache instance. Note that the deprecation only affects the bundle and using the bundle to configure doctrine/cache instances in Symfony Projects. The cache library itself is unaffected so far.