a270108bf6
The codepaths related to destroying associations asynchronously now consider when query constraints are present. In most cases, this means interpreting the primary key as an array of columns, and identifying associated records by a tuple of these columns, where previously this would've been a single ID. In each of the callsites, we use branching. This is done to maintain backwards compatibility and ensure the signature of the destroy job remains stable: it has consumers outside of Rails. |
||
|---|---|---|
| .. | ||
| destroy_association_async_job_test.rb | ||
| destroy_association_async_test.rb | ||
| helper.rb | ||
| job_runtime_test.rb | ||
| unloadable_base_job.rb | ||