Frederick Cheung wrote: > On 16 Jan 2009, at 20:44, Wes Gamble wrote: > >> When the Invoice class is loaded, all of its class level association >> directives are executed. When it hits the one that doesn't have a >> backing table, it fails. > > So it's at the point where the class (not the data) is loaded that the > problem occurs ? You might be in a tight spot then because it's going > to be hard to remove the association before the class exists.
Actually, the class needs to exist and I just need to temporarily remove the association. > define a new class Invoice < ActiveRecord::Base inside your fixture > generation code. if you don't need any of Invoice's methods then > you're fine with just this I need to be able to do a find on Invoice, which is why I have the problem in the first place, so this probably won't work. > Override ActiveRecord::Base.has_many to check if self is invoice and > the association name is the bad one. if it is, do nothing. if not let > the normal code run. This may work and I will give it a shot. Thanks for the idea. Wes -- 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 -~----------~----~----~----~------~----~------~--~---
