On 19 Feb 2009, at 20:50, dino d. wrote:

>
> This works fine, unless I enable config.cache_classes, then, the first
> user who accesses the site after the server is restarted gets his id
> set to current_user, and everyone else afterward gets the first guy's
> user_id set in the association.
>
> So, is there a way to disable only model caching, and cache everything
> else? Or, is this a  bug?
>

This isn't a bug - you're relying on something you should be relying  
on. The reflection builds the sql statement it needs to load the  
association but caches that sql thereafter.
I don't think there's a way round this without changing the way you're  
doing things.

Fred
> Thanks for any help,
> Dino
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to