diff options
| author | Ryuta Kamizono <kamipo@gmail.com> | 2018-08-20 23:41:45 +0900 |
|---|---|---|
| committer | Ryuta Kamizono <kamipo@gmail.com> | 2018-08-21 00:01:38 +0900 |
| commit | 96cd16bdeec661c9ecf1a83ca41a2cb22f435af9 (patch) | |
| tree | e13a9198b23dcffc75c1588a1fd51fe936c45968 /activemodel/lib/active_model/attribute_mutation_tracker.rb | |
| parent | ffca883908432f61a1fefdbcef5b1c10a7223acb (diff) | |
| download | rails-96cd16bdeec661c9ecf1a83ca41a2cb22f435af9.tar.gz rails-96cd16bdeec661c9ecf1a83ca41a2cb22f435af9.tar.bz2 rails-96cd16bdeec661c9ecf1a83ca41a2cb22f435af9.zip | |
Fix merging relation that order including `?`
The `Relation::Merger` has a problem that order values would be merged
as nested array.
That was caused an issue #33664 since if array value is passed to
`order` and first element in the array includes `?`, the array is
regarded as a prepared statement and bind variables.
https://api.rubyonrails.org/classes/ActiveRecord/Sanitization/ClassMethods.html#method-i-sanitize_sql_for_order
Just merging that as splat args like other values would fix the issue.
Fixes #33664.
Diffstat (limited to 'activemodel/lib/active_model/attribute_mutation_tracker.rb')
0 files changed, 0 insertions, 0 deletions