one use case would be merging updates from two different sources 1. 1st set of attribute values (from source a) modifies a value
2. 2nd set of attribute values (from source b - which your application decides has precedence) restores one or more of the original values 3. save update(s) +1 for a nice patch... good understanding of the mechanism On Aug 21, 12:56 am, "Damian Janowski" <[EMAIL PROTECTED]> wrote: > On Thu, Aug 21, 2008 at 1:54 AM, Ben Munat <[EMAIL PROTECTED]> wrote: > > Seems pretty straightforward: if you change an attribute and then change > > it back to the value it currently has in the db, it should no longer be > > considered dirty. > > Yeah, I understand the idea. I'm just asking what the use case is in > real world code because I can't think of any. > > Although it looks good in script/console, maybe the overhead is not worth > it... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
