Ryuta Kamizono 947a5de75d Don't use explicit references for join aliases ... As the API doc shows, `references` should be given table names. https://api.rubyonrails.org/classes/ActiveRecord/QueryMethods.html#method-i-references However, people (and test cases in the our codebase) sometimes give association names for `references`. Since the API example and all test cases in the codebase use symbols as arguments, so I regarded symbols as user given values in #40106. But as #40743 indicates, people also use string association names, it would have unexpected side-effect especially if singular association names given. As much as possible to avoid to use user given values, mark internal references for `where` and use only them for join aliases. Fixes #40743.		2020-12-04 15:19:20 +09:00
..
active_record	Don't use explicit references for join aliases	2020-12-04 15:19:20 +09:00
arel	Properly support reverse_order on relations with nulls_first or nulls_last calls	2020-09-08 11:20:46 -04:00
rails/generators	The abstract parent class file generated via generator should not be pluralized	2020-08-02 22:25:57 +05:30
active_record.rb	Destroy associations in a background job.	2020-09-24 14:24:15 -04:00
arel.rb