Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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 issues, but are there any major issues that anyone should be aware of before enabling it for an already built Rails 3.1 application?
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.