> crappy = Tagging.new > post.taggings << crappy > post.save
This saving will always be required, because adding a new object to an association should never have the side effect of actually saving the Tagging object here too. That would be really unexpected imho. For us, ActiveRecord is not the default standard on how things behave. We like to create something that fits the Ruby idiom of behaving like a developer expects. Saving objects as a side-effect of just adding it to an association does not really fit that principle of least surprise. These things notwithstanding, the has :through code is not up to par, so there probably will be issues. We're not yet sure on how to solve all of these problems, so that will take some discussion too. -- Regards, Dirkjan Bussink --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
