Download the PHP package easytek/doctrine-cache-invalidator-bundle without Composer
On this page you can find all versions of the php package easytek/doctrine-cache-invalidator-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download easytek/doctrine-cache-invalidator-bundle
More information about easytek/doctrine-cache-invalidator-bundle
Files in easytek/doctrine-cache-invalidator-bundle
Package doctrine-cache-invalidator-bundle
Short Description Invalidate easily your doctrine cache
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package doctrine-cache-invalidator-bundle
DoctrineCacheInvalidationBundle
Invalidate your doctrine cache easily.
This bundle is still a work in progress.
ToDo
- Define the invalidations rules in the bundle configuration instead of a class ?
- Add some tests.
- Add Doctrine 2.3 wildcard invalidation syntax.
Install
Use
Create this service :
Then you add it in your services file configuration :
Then you have to fill the array returned by the getClasses method of your service. The array contains a key for each doctrine entity class you want to work on. This key is associated with an array of invalidation rules, each invalidation rule is also an array, containing the two following informations :
- The cache id pattern, which can contain {attribute}, the same way you do in Twig.
- The entity changes triggering the invalidation, it can be "insert", "update", "delete" or "*" wich regroup the first three.
Example :
This means, when a Category entity will be either inserted, updated or deleted, the cache id 'category_{id}' (where {id} is replaced by $category->getId()) will be cleared.
