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.

Hello With Symfony 3.3 whenever I try any combination of doctrine:cache:clear ( dev/prod), it will throw the error

PHP Fatal error: Class 'Memcached' not found in /Users/user/Sites/Symfony1/vendor/doctrine/doctrine-cache-bundle/Tests/Functional/Fixtures/Memcached.php on line 6

Also, I read somewhere that doctrine-cache-bundle might require doctrine-fixtures-bundle, and I tried to install that, but again the same error is thrown on installation as per:

An error occurred when executing the "'cache:clear --no-warmup'" command:

I do have Memcached extension enabled on php ( Memcached version 3.0.4 as per phpinfo() ). Actually I am using Symfony's memcached adapter to cache query results per :

use Symfony\Component\Cache\Adapter\MemcachedAdapter;

I have to say that I am more than a bit confused with the overlap between Symfony's cache, ORM cache and doctrine-cache-bundle. Not sure If or how to use them together and the documentation is not at all clear.

In any case, here is my config.yml

` framework: cache: app: cache.adapter.memcached default_memcached_provider: "memcached://127.0.0.1:11211" ... orm: ... entity_managers: default: metadata_cache_driver: memcached result_cache_driver: type: memcached host: 127.0.0.1 port: 11211 instance_class: Memcached query_cache_driver: memcached

doctrine_cache: aliases: mem_cached_meta: my_memcached_cache_metadata mem_cached_query: my_memcached_cache_query mem_cached_result: my_memcached_cache_result providers: my_memcached_cache_metadata: type: memcached namespace: metadata_cache_ns aliases: - mem_cached_meta my_memcached_cache_query: type: memcached namespace: query_cache_ns aliases: - mem_cached_query my_memcached_cache_result: type: memcached namespace: result_cache_ns aliases: - mem_cached_result`

As I just installed Symfony 3.4, I get the following error:

Call to undefined method Doctrine\Bundle\DoctrineCacheBundle\Command\ContainsCommand::getDefaultName()

I believe this can be solved by updating the tags for the service definitions of the commands in Resources/services.xml

<services>
        <service id="doctrine_cache.contains_command" class="Doctrine\Bundle\DoctrineCacheBundle\Command\ContainsCommand">
            <tag name="console.command" />
        </service>
        <service id="doctrine_cache.delete_command" class="Doctrine\Bundle\DoctrineCacheBundle\Command\DeleteCommand">
            <tag name="console.command" />
        </service>
        <service id="doctrine_cache.flush_command" class="Doctrine\Bundle\DoctrineCacheBundle\Command\FlushCommand">
            <tag name="console.command" />
        </service>
        <service id="doctrine_cache.stats_command" class="Doctrine\Bundle\DoctrineCacheBundle\Command\StatsCommand">
            <tag name="console.command" />
        </service>
</services>

Would become:

<services>
        <service id="doctrine_cache.contains_command" class="Doctrine\Bundle\DoctrineCacheBundle\Command\ContainsCommand">
            <tag name="console.command" command="doctrine:cache:contains" />
        </service>
        <service id="doctrine_cache.delete_command" class="Doctrine\Bundle\DoctrineCacheBundle\Command\DeleteCommand">
            <tag name="console.command" command="doctrine:cache:delete" />
        </service>
        <service id="doctrine_cache.flush_command" class="Doctrine\Bundle\DoctrineCacheBundle\Command\FlushCommand">
            <tag name="console.command" command="doctrine:cache:flush" />
        </service>
        <service id="doctrine_cache.stats_command" class="Doctrine\Bundle\DoctrineCacheBundle\Command\StatsCommand">
            <tag name="console.command" command="doctrine:cache:stats" />
        </service>
</services>

in case cache provider only use on other services argument, so i dont need that provider set as public service.

for example i use doctrine cache for caching the validation metadata

# service.yml
services:
    app.cache.validation:
        class: "Symfony\\Component\\Validator\\Mapping\\Cache\\DoctrineCache"
        arguments: ["@doctrine_cache.providers.validation_cache"]
        public: false

# config.yml
doctrine_cache:
    providers:
        validation_cache:
            namespace: "validation_cache:"
            redis:
                host: "..."
                port: "..."
                database: "..."

framework:
    validation:
        cache: app.cache.validation

the service doctrine_cache.providers.validation_cache just as other service arguments.

so i think it would be great if it can set as 'public' option

# config.yml
doctrine_cache:
    providers:
        validation_cache:
            namespace: "validation_cache:"
            redis:
                host: "..."
                port: "..."
                database: "..."
            public: false

Currently, providers are not loaded lazy and there's no easy way (or I didn't find out) to let them load lazy. The problem is, that if you inject such a provider into a class in symfony, there is no easy way to catch an exception happening during constructing the class. And at least in the redis provider, an exception happens simply when the redis server is not reachable (which for a cache shouldn't lead in an not easy catchable exception). When lazy loading the provider, we can handle this case with a common try/catch construct in the get/set calls

[Symfony\Component\Debug\Exception\ContextErrorException] Notice: Undefined index: scheme in /vendor/doctrine/doctrine-cache-bundle/DependencyInjection/Definition/PredisDefinition.php line 49

possibly after 8290005dd8366484e61a47b62ee75f4fe18abede

\app\config\config.yml

    orm:
        entity_managers:
            default:
                second_level_cache:
                    region_cache_driver:
                        type: predis
                    enabled: true

Fixes #76

I believe symfony/security-acl isn't used by anything, but this bundle provides a cache layer for it (if you're using it).

This should also help https://github.com/doctrine/DoctrineBundle/pull/486#issuecomment-159664695

Thanks!

WORK IN PROGRESS

Architecture:

• A service tag is added to provider services in the extension.
• A compiler pass is used to replace the provider class with a proxy. For performance, this only happens if the kernel is in debug mode.
• The proxies log certain calls and data to a central LogMaster.
• The DataCollector uses the LogMaster to retrieve and display data in the debug toolbar and panel.
• The LogMaster can be retrieved and used for any other purpose that needs access the logs.

To do:

• [ ] Need a icon for the debug toolbar.
• [x] Finish profiler panel display
• [x] Doc blocks
• [ ] Tests
• [x] General cleanup

... more

Metadata caching fails on PHP7 phpredis because of igbinary. So is there a way to change default RedisCache so that serializer is Redis::SERIALIZER_PHP and not Redis::SERIALIZER_IGBINARY ?

I don't want to recompile a phpredis extension without igbinary in it.

New persistent configuration option for Redis introduced. It allows the connection to be persistent by internally switching connection method from \Redis::connect to \Redis::pconnect

There is no possibility to open an issue on doctrine/cache, so I'll open it here.

I use Doctrine Cache Bundle with Memcache and, when I do this:

$memcache->setNamespace('mynamespace');
$memcache->save($mykey, 'some-data-here', 3600);
$result = $memcache->delete($mykey);

I always get the following Notice:

PHP Notice: MemcachePool::delete(): Server localhost (tcp 11211, udp 0) failed with: CLIENT_ERROR bad command line format. Usage: delete [noreply]

If I replace internally in the library this:

return $this->memcache->delete($id) || ! $this->doContains($id);

with this:

return $this->memcache->delete($id, 0) || ! $this->doContains($id);

Then I no longer get the notice.

This is quite interesting because, according to PHP documentation:

It's not recommended to use the timeout parameter.

Is anyone else experiencing this problem ? Or is it just me ? I suspect most people use memcache when using this library. So how come is it's not reported/fixed by now ?