[Rails-core] Re: RFC: associations with :accessible => true should allow updating

[David Dollar]

On a related-yet-slightly-different-topic note:

p = Project.find(:first)
p.tasks.first.name = 'New Name'
p.save

does not update the Task in the database. I'd like to get some
thoughts/opinions on using dirty tracking to make cascadable saves
possible.

If I could cascade the saves, it becomes a lot easier to bubble up
validations in a format that makes sense for nested associations.

On Jul 18, 2008, at 7:16 PM, Ryan Bates wrote:

On Jul 18, 1:47 pm, Josh Susser <[EMAIL PROTECTED]> wrote:

Yep, exactly.  I talked with David Dollar on IRC about this.  I've

update the associated models in a before_validation callback, rather
than in the setter.  That keeps everything in one transaction and

approach of splitting the setters into two pieces for create and

I've still yet to figure out a really nice way to handle that.

done this in a way that is similar to your recipe in ARR, but I create/ makes it a little easier to handle validation issues. I did like your update. The one thing that keeps bugging me though is doing deletes -

I'm going to have to try using a before_validation callback. Regarding
deletes, are you not happy with removing all children that are missing
in the params hash (as the recipe does)? I suppose it is a little
dangerous, but I can't think of an alternative solution which is close
to the same simplicity.

Ryan

--~--~---------~--~----~------------~-------~--~----~

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
-~----------~----~----~----~------~----~------~--~---

You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.

smime.p7s
Description: S/MIME cryptographic signature