TEST_CODEOWNERS/rails
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[ci skip] Clarify the "Serialized Attributes" section

Browse Source 
Mention that the change in nil handling for serialized attributes
affects custom coders.
This commit is contained in:
Vasily Polovnyov 2014-07-26 22:34:56 +04:00
parent 9c8826bcd2
commit 4bfd0cef5b
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
guides/source/upgrading_ruby_on_rails.md
View File

@ -54,7 +54,8 @@ NOTE: This section is a work in progress.
### Serialized attributes
When assigning `nil` to a serialized attribute, it will be saved to the database
When using a custom coder (e.g. `serialize :metadata, JSON`),
assigning `nil` to a serialized attribute will save it to the database
as `NULL` instead of passing the `nil` value through the coder (e.g. `"null"`
when using the `JSON` coder).