diff options
| author | Ryuta Kamizono <kamipo@gmail.com> | 2018-07-31 08:17:45 +0900 |
|---|---|---|
| committer | Ryuta Kamizono <kamipo@gmail.com> | 2018-07-31 08:31:46 +0900 |
| commit | c83e30da27eafde79164ecb376e8a28ccc8d841f (patch) | |
| tree | 0fe10e509f684d4cee8e85d183f90e69acff84ea /activesupport/test/benchmarkable_test.rb | |
| parent | e8dd2bf85716f4aaf3ea4223e748e539589937f6 (diff) | |
| download | rails-c83e30da27eafde79164ecb376e8a28ccc8d841f.tar.gz rails-c83e30da27eafde79164ecb376e8a28ccc8d841f.tar.bz2 rails-c83e30da27eafde79164ecb376e8a28ccc8d841f.zip | |
Avoid extra scoping when using `Relation#update`
Since 9ac7dd4, class level `update`, `destroy`, and `delete` were placed
in the `Persistence` module as class methods.
But `Relation#update` without passing ids which was introduced at #11898
is not a class method, and it was caused the extra scoping regression
#33470.
I moved the relation method back into the `Relation` to fix the
regression.
Fixes #33470.
Diffstat (limited to 'activesupport/test/benchmarkable_test.rb')
0 files changed, 0 insertions, 0 deletions