> Michael, is the attribute that you're passing to the touch method a field of > type datetime or date? If not, then it only makes > sense that field that you're passing to the touch method is one of those.
It is "datetime". But anyway, just looking at the code for "touch" I can't see how it's is supposed to NOT always write updated_at - it uses write_attribute which as far as I found out only changes the in-memory object, there must be a "save" somewhere else and that goe4s through the usual validations etc. There's a lighthouse ticket for "touch" calling for it not to do validations (https://rails.lighthouseapp.com/projects/ 8994-ruby-on-rails/tickets/2520-patch-activerecordtouch-without- validations). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
