On Oct 30, 7:08 pm, John Small <[EMAIL PROTECTED]>
wrote:
> Roy Pardee wrote:
> > Well don't leave us hanging--how'd you fix it? ;-)
>
> Oh I thought I'd explained it in the previous message. I took the class
> definitions out of the module, and moved them into the rake file. That
> did the trick.
>
If you were previously using require to require files in your app then
that can screw things up big time.
Fred
> I suspect that the problem has something to do with the associations
> being to ActiveRecords that are declared inside modules and then used
> outside those modules. But I've not had a chance to play around to find
> out.
>
> John Small
>
> --
> Posted viahttp://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-talk@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-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
