Voting starts in March for the Drupal Association Board election.
Entity cache puts core entities into Drupal's cache API.
Due to the entity loading changes in Drupal 7, no core patches are required.
Don't bother using this module if you're not also going to use http://drupal.org/project/memcache or http://drupal.org/project/redis - the purpose of entitycache is to allow queries to be offloaded from the database onto alternative storage. There are minimal, if any, gains from using it with the default database cache.
How to use it
This module has no user interface, if you enable it, entities will start being cached, if you disable it, they'll stop.
Supported core entities
- Taxonomy terms
- Taxonomy vocabularies
Support for contrib entities:
There is no automated support for contrib entities, to use entitycache for a contrib or custom entity:
- Create a cache_entity_$myentity table/bin.
- Specify EntityCacheDefaultEntityController as your controller class in hook_entity_info(), or extend it.
- Never update your entity tables outside of save/delete API calls.
Entity cache is now set up for automated testing on Drupal.org, see current HEAD status.
This module will not be ported to Drupal 8, because entity caching is supported in core:.
- Maintenance status: Actively maintained
- Development status: Maintenance fixes only
- Module categories: Performance and Scalability
- Reported installs: 31,394 sites currently report using this module. View usage statistics.
- Downloads: 579,137
- Automated tests: Enabled
- Last modified: October 16, 2015
- Stable releases are covered by the security advisory policy.
Look for the shield icon below.