Why shouldn't it be changed right away? Because the parent may be invalid.
Really, the problem is consistency. If are doing an update to the parent and children and the parent is invalid, the children may or may not be affected. The consistent way to handle it would be to not update the children until the parent is saved. IMHO Thanks, Tom On Oct 30, 11:32 am, sw0rdfish <[EMAIL PROTECTED]> wrote: > I don't think it's odd at all.... the only reason it's not saved until > the Parent is initially saved is if the parent has no ID, how cna you > assign parent_id to the child ( or the join table ). > > If you're modifying the children w/o touching the parent.... say > categories and posts in those categories.... It would be up to the > category model to validate any changes you make to it... and if you > changed a post in one of those categories... or changed the category > the post belonged to... why shouldn't it be changed right away? Why > would I need to re-validate the category? --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
