mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
e32fd534b5
The current behaviour of reverse_order, when presented with an existing order that is an Arel expression, is to ignore it. This isn't quite in keeping with how it handles Arel attributes (which it reverse) or arbitrary strings (which throw an exception). The easy path would be to throw an exception, but we don't have to. Any SQL expression that is a valid default sort expression can be reversed with DESC. It follows that if there's an existing Arel::Nodes::NodeExpression that is not already wrapped with an Arel::Nodes::Ordering, then it can be reversed with DESC. |
||
|---|---|---|
| .. | ||
| batches | ||
| predicate_builder | ||
| batches.rb | ||
| calculations.rb | ||
| delegation.rb | ||
| finder_methods.rb | ||
| from_clause.rb | ||
| merger.rb | ||
| predicate_builder.rb | ||
| query_attribute.rb | ||
| query_methods.rb | ||
| record_fetch_warning.rb | ||
| spawn_methods.rb | ||
| where_clause.rb | ||