From d1d5832e7d31b49134af4cdafaf19faded28c856 Mon Sep 17 00:00:00 2001 From: Alexander Makarov Date: Tue, 16 Aug 2016 13:01:17 +0300 Subject: [PATCH] Fix typo [skip ci] (#12169) (reverted from commit a3cd5542799f64e8b61b4f8b5272701e910eee72) --- docs/guide/db-active-record.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/db-active-record.md b/docs/guide/db-active-record.md index fbbfbf8..41e236b 100644 --- a/docs/guide/db-active-record.md +++ b/docs/guide/db-active-record.md @@ -250,7 +250,7 @@ named in this way. If you are concerned about code style consistency, you should ### Data Transformation It often happens that the data being entered and/or displayed are in a format which is different from the one used in -storing the data in a database. For example, in the database you are storing customer's birthdays as UNIX timestamps +storing the data in a database. For example, in the database you are storing customers' birthdays as UNIX timestamps (which is not a good design, though), while in most cases you would like to manipulate birthdays as strings in the format of `'YYYY/MM/DD'`. To achieve this goal, you can define *data transformation* methods in the `Customer` Active Record class like the following: