This is not about query caching, but about having only one instance of
the object within a session.
Say, Post.find(1) and User.find(1).posts.detect{|it| it.id == 1} would
return you different objects.
Ideal identity map would fix that problem.On Oct 11, 7:03 pm, Marnen Laibow-Koser <[email protected]> wrote: > Marnen Laibow-Koser wrote: > > golubevpavel wrote: > >> Thanks for your reply, David. > > >> Agree, I've got several ideas myself. > >> But most of them are kinda specific. > >> Well, one of ideas is to implement identity map for ActiveRecord. > >> I need it, but I am not sure, if community does. That's why I'm > >> asking. > > > You're a member of the community. If you need it, write it, release it, > > and see what happens! > > ...however, if by "identity map" you mean caching queries so that you > don't retrieve the same DB query twice in the course of one HTTP > request, ActiveRecord already does this. > > > Best, > > -- > > Marnen Laibow-Koser > >http://www.marnen.org > > [email protected] > > -- > Posted viahttp://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

