On 17 Aug 2009, at 01:59, Dan Kubb (dkubb) wrote:
> Yeah, the more I think about it the more I believe that > Resource#update should throw an exception when called on a dirty > resource. I don't think I'm going to bother exploring the variable > stashing, as there are too many weird edge cases for such little > benefit. I think this is the sanest thing to do in the mean time. And while I can benefits to having Model, Collection and Resource share a similar API, I'm still unconvinced that #update actually applies to Resource at all... Ashley -- http://www.patchspace.co.uk/ http://www.linkedin.com/in/ashleymoran http://aviewfromafar.net/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
