On Nov 8, 4:07 am, Aliaksey Kandratsenka <[EMAIL PROTECTED]> wrote: > ... so that people don't try to preserve instances or > classes between requests
... currently, very easy to do, if you store ActiveRecord instances in ActiveSupport's memory cache store. With the current Rails reloading behavior in development, you need to add additional logic to your app to not cache AR instances in development, or avoid this practice entirely, neither of which are attractive options, imo. As I understand it, if we do allow AR instances to persist between requests, there'd only be an issue when you modify the class of an instance that was cached -- in this case, you'd need to restart the server. But I think that makes intuitive sense -- cached instances would then be out-of-sync with the current class definition. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
