Performance Improvements for has_many through queries #205
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.
This PR introduces two optional improvements to conditions that allow for more efficient queries. These are specifically for conditions referencing a has_many :through association.
The two features are:
.with_through_id_relationship
- this is simply a bool flag to tell Refine that we expect this to be an id attribute through an association. That way we can shortcut our queries to simply fetch the source primary_key and the target primary_key with the joins table rather than having to run two separate inner_joins to bridge the 3 tables.with_forced_index(index_name)
- Adds aFORCE INDEX()
wrapper with the FROM query in the subquery generated for the condition.So it will change a query like
To