ReferenceDynamic - Save lots of irrelevant queries when finding backreferences #29381
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Follows up on 834f598 to fix a long-standing FIXME in the dynamic reference code.
Before
Checking for dynamic backreferences searched every other entity in the database, not just relevant ones, with a fixme about it in the code.
After
Fixme fixed.
Technical Details
When this code was first written most dynamic references had an open-ended
entity_table
target column which could theoretically join to anything. Over the years we've been adding whitelists to those columns since most of these entities were only intended for a handful of possible targets. So at the time of writing this fixme, there was no reliable way to use a whitelist to limit the scope of reference searches across the database. Now, for most entities, there is.A few are still missing whitelists so this grandfathers them in with the old behavior. For all the rest, finding references should be faster and make more sense.