Taken from entity.api.php:
For entity_crud_hook_entity_info():
* - entity cache: (optional) Whether entities should be cached using the cache
* system. Requires the entitycache module to be installed and enabled. As
* cached entities are only retrieved by id key, the cache would not apply to
* exportable entities retrieved by name key. If enabled, 'field cache' is
* obsolete and should be disabled. Defaults to FALSE.
There is also something in hook_entity_property_info():
* - clear: (optional) An array of property names, of which the cache should
* be cleared too once this property is updated. As a rule of thumb any
* duplicated properties should be avoided though.
So it seems very straightforward.
Comments
Comment #1
fmizzell commentedI just added a new branch to the repository containing the little bit of glue code necessary for eck to work with entitycache. The code is not complete as it does not create caching tables for new entity types created after enabling the module, but It will create tables for all you entity types at the time of enabling the module.
Comment #2
steven jones commentedI've taken the work in the caching branch, refactored a little and made it work when entity types are added or removed, this patch is against 7.x-2.x.
Comment #3
fmizzell commented