tags_count only need to join on the taggable's table if using STI #904
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.
The INNER JOIN on the taggable's table name is only necessary if the taggable is using single table inheritance. Otherwise, the IN subquery generated in
generate_tagging_scope_in_clause
, which retrieves a list of the taggable's IDs based on the current scope, is sufficient.tagging_conditions
also already includes making sure that taggable_type is the one that corresponds to the taggable.The removal of the extra inner join in non-STI cases improves performance quite significantly for tag counts.
Take into consideration
Project.tag_counts_on(:tags)
, andProject.where("client is not null").tag_counts_on(:tag)
Current:
With this change:
Fixes #724