On 10/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi Rick, > > > Ah, I think I left that out on accident on one of my recent commits. > > I'll check it out. What tests are failing? The AR test suite was all > > passing when I committed. > > The problem occurs when you have a has_many :through a has_many which > has conditions. > > Luckily, the AR fixtures have an instance of this type of relationship, > so I wrote a small test (http://pastie.caboo.se/17035) that fails in > the current revision, but passes in r5263 (which I believe is the rev > before the change). > > Cheers, > Ian
I rolled back the changeset and documented the quirky behavior. Basically, conditions are usually interpolated in the context of the actual record. But since the record hasn't been loaded yet with eager loading, it's interpolated in the context of the class. This gives you access to the aliased_table_name method which probably comes in handy for those crazy eager include queries. Thanks for bringing this up, and let me know if this works out. -- Rick Olson http://weblog.techno-weenie.net http://mephistoblog.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
