Does anyone know the key issues that the Rails 3.1 IdentityMap feature has that has forced the feature to be disabled by default? I\'m sure that there are minor specific iss
When you look at the documentation the main issue raised is that objects managed in the Identity Map can not handle associations yet, so it's not quite ready for real world usage right now.
The documentation states clearly that the feature is still under development, so no one should really be using it in the wild.