@ ddollar: i cover some use cases in my patch where new_record? won't suffice.
http://rails.lighthouseapp.com/projects/8994/tickets/2089-add-arbasejust_created-to-differenciate-records#ticket-2089-3 which i guess i could just repeat here: 1. Where the find_or_create call is internal to a another wrapper method. 2. Where you need to operate on a saved record [most likely needing the id attribute]. @jose three tickets? i just see mine [from last month] and this one [from today]. and it looks like my implementation does a little more than what this one does which seems to simply wrap !new_record? with saved_record? [unless i'm missing something]? rsl On Wed, Mar 18, 2009 at 1:58 PM, David Dollar <[email protected]> wrote: > > Why not just use unless object.new_record? > > It seems like any of the saved/existing/etc_record? have potentially > non-obvious meanings. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
