Created a patched. http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2262-associations-are-picking-the-wrong-class
On Mar 17, 1:35 am, José Valim <[email protected]> wrote: > > Really? Despite namespace models have an issue, wouldn't this just be > > bad in general for all sorts of other reason? What if the model it > > chose was in a namespace for a plugin or something else vendor related? > > This is exactly what happened. I'm not using namespaces in my > application but I've installed Typus (http://github.com/fesplugas/ > typus) as plugin and since it has Typus::User, my application (Rails > 2.3.2) started to pick up Typus::User instead of User when doing > Account.build_user. > > > Is the fix crazy or simple? > > The fix is simple: 3 files changed, 12 insertions(+), 3 deletions(-). > > >http://m.onkey.org/2007/12/9/namespaced-models > >http://stackoverflow.com/questions/601768?sort=oldest > >http://www.strictlyuntyped.com/2008/08/activerecord-can-haz-namespace... > > Ryan Angilly, those posts say: "don't use namespaced models". But as > Ken pointed out, your plugins, gems, etc can use. > If you listening their advice and not using namespaced models, the fix > won't affect you. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
