On Wed, Aug 26, 2009 at 11:21 AM, Rob Biedenharn<r...@agileconsultingllc.com> wrote: > Actually, there's no need to nil the id because you can't mass-assign > the id. > > b = B.new(a.attributes) > > would have exactly the same effect.
I have 47 models with matching history models that will disagree. If I don't nil the id it complains. -- Greg Donald http://destiney.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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
