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.
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 via http://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 [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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
