> Would be a patch useful, if currently there are no ways, regarding > this matter?
It sucks that this is inconsistent, but I think this is probably going to be a pretty tough problem for you to solve with a patch. Because the presence of an object in the has_many :through collection requires the existence of a record in the association table. Figuring out how to handle the different permutations of validation methods along the chain will probably be a little difficult. In your case you could probably try either using the full set of associated classes (i.e. creating the ReportReason object in your controller). Or alternatively create and validate the reason object on its own. Mixing transient and persistent objects in a single graph leads to some strange issues like this, so you're probably better off avoiding the potential problems altogether. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
