diff options
author | Sean Griffin <sean@thoughtbot.com> | 2014-12-16 15:19:47 -0700 |
---|---|---|
committer | Sean Griffin <sean@thoughtbot.com> | 2014-12-16 15:23:05 -0700 |
commit | dd8b5fb9d30f355d4eab6376b8d9e025e90b14d3 (patch) | |
tree | 887b7851abeb0432bc013f362e396e2b2f0a0723 /README.md | |
parent | e4c9bd9828e107214d03a66679a89f669e3722fa (diff) | |
download | rails-dd8b5fb9d30f355d4eab6376b8d9e025e90b14d3.tar.gz rails-dd8b5fb9d30f355d4eab6376b8d9e025e90b14d3.tar.bz2 rails-dd8b5fb9d30f355d4eab6376b8d9e025e90b14d3.zip |
`update_column` take ruby-land input, not database-land input
In the case of serialized columns, we would expect the unserialized
value as input, not the serialized value. The original issue which made
this distinction, #14163, introduced a bug. If you passed serialized
input to the method, it would double serialize when it was sent to the
database. You would see the wrong input upon reloading, or get an error
if you had a specific type on the serialized column.
To put it another way, `update_column` is a special case of
`update_all`, which would take `['a']` and not `['a'].to_yaml`, but you
would not pass data from `params` to it.
Fixes #18037
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions