On 11/16/06, leei <[EMAIL PROTECTED]> wrote: > > Unfortunately, it's in the middle of a complex app and I haven't been > able to reduce it. > > Actually, just trying to pull tracing data out (to show how it gets > cleared), I stumbled onto what is most probably the solution. It tuns > out that I was mistaken, this is between requests in development mode, > so the class at issue *should* be reloaded, but isn't. It seems to > have been cleared, but is still hanging around and the class reload has > not taken place. I discovered this by putting a breakpoint into the > class definition itself, which was triggered for the first request, but > not the second. Running with cache_classes = true seems to work just > fine... > > Are there any known bugs with cache_classes in edge? How has this > changed since 1.1.6? The bug seems to be that my AR class is cleared > of associations (seemingly in preparation for reload), but it does not > reload on reference and instead tries to use the existing "empty" class > definition.
Reflections refer to the class object which is reloaded. I'd need to know a little more about why you have kept a reflection around between reloading classes it refers to. jeremy --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
