I disagree... that should be up to the developer to check... like my example, why do I need to validate the category, each time I post?
My feeling is that if it's something that you need to have, then create a before_filter and have it validate, otherwise you're validating things that never change... although I can see your argument for consistency... I still have no problem with the way it is now... That being said, my opinion rarely matter :P On Oct 30, 1:05 pm, TomRossi7 <[EMAIL PROTECTED]> wrote: > 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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
