Hello all, I was hoping someone could explain to me why both sides of a has_many :through association need to not be new_records? Wouldn't the save be able to succeed if the object with the has_many :through association was the only new_record?
It seems to me that because something like p = posts.new p.taggings << Tagging.new(:tag_id => 1) p.save works, that something like p = posts.new p.tags << Tags.create p.save should be able to work since rails should be able to do essentially what happens in the first example under the covers. Maybe it's difficult to manage what p.tags returns before you've saved it, or something like that? Is it the sort of thing that could be done, it's just high effort, or is there some impossible case I'm missing? After I started thinking about it I became very curious, so I googled around, searched trac, but didn't find anything. I'd be very appreciative for any enlightenment on the subject. Thanks, Jason --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@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-core?hl=en -~----------~----~----~----~------~----~------~--~---
