From 6ae302c9da8462aef5394cef356b323d50bd799c Mon Sep 17 00:00:00 2001 From: Saverio Miroddi Date: Wed, 8 Aug 2018 16:06:06 +0200 Subject: ActiveRecord Basics guide: correct explanation of the `updated_at` logic [ci skip] It's misleanding/incorrect to state that `updated_at` is set on updates, since creation != update (and the column is actually set on creation, too). --- guides/source/active_record_basics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'guides') diff --git a/guides/source/active_record_basics.md b/guides/source/active_record_basics.md index 2f85b765a3..ef5ddb5282 100644 --- a/guides/source/active_record_basics.md +++ b/guides/source/active_record_basics.md @@ -115,7 +115,7 @@ to Active Record instances: * `created_at` - Automatically gets set to the current date and time when the record is first created. * `updated_at` - Automatically gets set to the current date and time whenever - the record is updated. + the record is created or updated. * `lock_version` - Adds [optimistic locking](http://api.rubyonrails.org/classes/ActiveRecord/Locking.html) to a model. -- cgit v1.2.3