Hi guys, same problem here.
> As for my opinion on the matter, I think AR should not be setting the > time itself and it should be using the database NOW function. Totally agree. I feel like the Rails' behavior is very counterintuitive here. Have you taken the discussion else where? I would love to see a discussion on this on the rails repo (https://github.com/rails/rails). Maybe this is something that could be tackled with Rails 5 or 6. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/a19b578757fbc8ff8ced65bc187256dc%40ruby-forum.com. For more options, visit https://groups.google.com/d/optout.
