mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
![]() With the old implementation, the bind values were created, and then we search the attributes for `Relation` objects, and merge them. This completely ignores the order that the actual `where` clause will use. If all non-relation where parameters are before the relations, it will work. However, if we query on both a relation and a value, with the value coming second, it breaks. The order of the hash should not affect the final query (especially since hashes being ordered is an implementation detail) |
||
---|---|---|
.. | ||
predicate_builder | ||
batches.rb | ||
calculations.rb | ||
delegation.rb | ||
finder_methods.rb | ||
merger.rb | ||
predicate_builder.rb | ||
query_methods.rb | ||
spawn_methods.rb |