Optimize DB accesses by using an SQL JOIN when retrieving a user. (opr #679) #56
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.
Datastore.find_user()
is used on every page load to verify the user inthe current session; until now,
find_user()
would trigger 2+ DBaccesses, since the
roles
relationship uses lazy loading by default.This is useful to reduce the rows accessed when retrieving multiple
users from the DB.
However, in
find_user()
we always retrieve only one, soit makes sense to retrieve all roles in one SQL operation instead of
always triggering 2 or more.
This would be unnecessary if the
roles
relationship was defined withlazy="joined"
. However, that would greatly increase the number of rowsaccessed on all queries (even when querying all users), so I think it's
better to be selective and optimize only these accesses which happen on
every page load.