mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
dd8b5fb9d3
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 |
||
---|---|---|
.. | ||
active_record | ||
rails/generators | ||
active_record.rb |