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

fmizzell’s picture

Status: Active » Needs work

I 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.

steven jones’s picture

Status: Needs work » Needs review
StatusFileSize
new5.07 KB

I'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.

fmizzell’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

  • Commit 5717c3a on 7.x-2.x, 7.x-2.x-property-widgets, 7.x-3.x, entity_reference, 7.x-3.x-settings, 7.x-2.0.x, 7.x-2.1.x authored by Steven Jones, committed by fmizzell:
    #1506468 EntityCache support
    

  • Commit 5717c3a on 7.x-2.x, 7.x-2.x-property-widgets, 7.x-3.x, entity_reference, 7.x-3.x-settings, 7.x-2.0.x, 7.x-2.1.x authored by Steven Jones, committed by fmizzell:
    #1506468 EntityCache support