Weave Code
Doctrine Cache Extension Laravel Package
openclassrooms/doctrine-cache-extension
A small extension to Doctrine's cache library that adds extra cache adapters and helpers, making it easier to wire alternative backends into Doctrine ORM and Symfony applications.
Library extending doctrine cache capabilities
Frequently asked questions about Doctrine Cache Extension
- What does openclassrooms/doctrine-cache-extension do?
- It is a small extension to doctrine/cache that adds extra cache adapters and wiring helpers. Its role is to augment Doctrine Cache rather than replace it, so it inherits the constraints of that library. The package is best understood as legacy sugar for Doctrine-based caching, not a standalone caching framework.
- Is openclassrooms/doctrine-cache-extension compatible with Laravel?
- Only indirectly. Laravel uses Illuminate\Cache and PSR-6/PSR-16 contracts, while this package extends doctrine/cache, which Doctrine ORM 3.x has removed. It fits a legacy Laravel application only if Doctrine ORM 2.x or Doctrine DBAL is already using doctrine/cache. Adding it to a modern Laravel stack would create a second parallel caching abstraction.
- How do I install openclassrooms/doctrine-cache-extension?
- Install it with Composer using composer require openclassrooms/doctrine-cache-extension. You should first confirm that the version constraint resolves against your existing doctrine/cache and PHP versions. Because the package targets a deprecated upstream, test the resolver output on your target PHP before committing.
- Does openclassrooms/doctrine-cache-extension work with Doctrine ORM 3.x or PSR-6 caching?
- No. Doctrine ORM 3.x removed doctrine/cache, and this package is a thin extension to that deprecated library. It is not a PSR-6 or PSR-16 implementation and should not be used as a bridge to symfony/cache or Laravel's cache contracts. Modern stacks should use PSR-6-compatible caching directly.
- What extra cache adapters or helpers does openclassrooms/doctrine-cache-extension add over doctrine/cache?
- The assessment describes it as a narrow augmentation that may add cache providers, namespacing, or dependency-injection wiring helpers. The exact surface is not documented in the provided README excerpt, so verify it by diffing the source against doctrine/cache. Treat any adapter list you find as legacy-specific and confirm it matches your Doctrine version.
- Is openclassrooms/doctrine-cache-extension abandoned or still maintained?
- The assessment flags it as high abandonment risk: zero stars, zero dependents, and a one-line description suggest an internal OpenClassrooms utility that was open-sourced and never widely adopted. Its upstream, doctrine/cache, is also formally deprecated and end-of-life. Assume no future security or PHP-version patches from either layer unless you verify recent commits and releases.
- Can I use openclassrooms/doctrine-cache-extension in a new Laravel project?
- It is not a good foundation for a new project. The TPM assessment explicitly says there is no scenario where this package is the right foundation for greenfield caching architecture. Use Laravel's cache layer or PSR-6/PSR-16 packages instead, and treat this extension only as a legacy compatibility option.
- How does openclassrooms/doctrine-cache-extension compare to symfony/cache or Laravel's cache?
- It is not a replacement for either. symfony/cache and Laravel's cache provide modern PSR-6/PSR-16 abstractions, while this package extends the deprecated doctrine/cache library. Using it alongside a modern cache stack creates two parallel abstractions and a migration liability, so prefer the native cache component for your framework.
- Which PHP versions does openclassrooms/doctrine-cache-extension support?
- The provided context does not list exact PHP versions. The assessment notes loose constraints against a deprecated upstream, which can cause Composer resolver conflicts on PHP or Symfony upgrades. Check the package's composer.json and run composer why-not or composer update --dry-run on your target PHP before adopting it.
- Should I fork or vendor openclassrooms/doctrine-cache-extension for production use?
- Only if it is already in your dependency tree and you accept a fork-on-first-bug maintenance model. The assessment says adoption implies defining an exit path up front and confirming an internal owner willing to vendor or fork it. For new work, avoid introducing it and use maintained PSR-6 caching instead.
Weaver
How can I help you explore Laravel packages today?