On Jul 27, 2006, at 7:47 AM, Manfred Stienstra wrote:
On 27-jul-2006, at 16:20, Jonathan Viney wrote:
Forgot to attach the patch! Here it is ...
There's a good reason for this:
p = Person.find :first
p.user.name = 'New Name'
p.save
That's a valid point. But did you read Jonathan's patch? It covers
that case where you're dealing with new records just fine. I think
the issue he was correcting was that has_one *always* saves the child
object, not just for new records.
--
Josh Susser
http://blog.hasmanythrough.com
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
