add explicit inverse_of to scoped user_levels association#10745
Merged
Conversation
Closed
Contributor
|
LGTM. |
ashercodeorg
approved these changes
Sep 20, 2016
Contributor
|
Should we do an audit and see if there is anywhere else in our codebase missing such an annotation? |
Contributor
Author
|
yeah, i think an audit-pass through our ActiveRecord models for this sort of easy optimization could be helpful. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rails ActiveRecord has an optimization-feature called 'inverse associations' (see "Setting Inverses" API documentation), which optimizes query chains such as
parent -> child -> parentgoing betweenhas_manyandbelongs_toassociations e.g.,user.user_levels[0].user, by reusing the original ActiveRecord object rather than re-querying the database to recreate it.Since Rails 4.1, ActiveRecord tries to automatically infer
inverse_ofrelations based on the class names- however, custom scopes (such as-> {order 'id desc'}) cause the automatic inference to be disabled, so they need to be explicitly added in order for this optimization to be applied.Before:
After: