Greg, > I typically either do all the changes at once using update_attributes > () or I'll assign changes directly to attributes conditionally as I'm > checking various things, then do a save at the end of a loop. I don't > think I've ever used update() in production, only when messing around;
I probably should've clarified this before but Resource#update_attributes was renamed to Resource#update in the 0.10 series. Also the behavior between Model#update, Collection#update and Resource#update is being made more consistent across the board. I started this thread mostly because the behavior for Resource#update_attributes and Resource#update had never been defined explicitly in the case where it was called on a dirty resource. -- Dan Kubb (dkubb) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
