DataMapper ORM v1.8.2

[eluser]WanWizard[/eluser]
No.

Caching in my opinion should not be an ORM feature, you should deal with that in your controller.

If your ORM caches, it can only cache based on the generated query, and use (for example) a hash of that as cache key. This means that since it has a random key, you can not access, update or delete the cached item from the outside.

Given the fact that you would want your CRUD functions to delete the cache (you have updated a record), you need the cache key to be known.

If does however do quite a lot of internal caching. It will for example never fetch and hydrate the same record twice, it will cache query results.

It comes with tonnes of other features though, including built-in soft-delete en temporal support (versioning).