Cache non existing DB user #1672
Merged
Conversation
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
We always query the database backend. Even if we use a different one (ldap for example). Now we do this everytime we try to get a user object so caching that a user is not in the DB safes some queries on each request then (at least 2 what I found). Signed-off-by: Roeland Jago Douma <[email protected]>
|
@rullzer, thanks for your PR! By analyzing the history of the files in this pull request, we identified @Xenopathic, @DeepDiver1975 and @nickvergessen to be potential reviewers. |
Member
|
Bad luck with parallel requests, but I guess this is acceptable. 👍 |
Member
|
Should we update the flag on delete? |
Member
Author
|
We could. Altough it is probabaly not needed. Will result in at most one 1 extra query in that request. (the request where you delete a DB user). |
Member
|
LGTM |
LukasReschke
approved these changes
Oct 10, 2016
LukasReschke
added
4. to release
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.
We always query the database backend. Even if we use a different one
(ldap for example). Now we do this everytime we try to get a user object
so caching that a user is not in the DB safes some queries on each
request then (at least 2 what I found).
CC: @nickvergessen @MorrisJobke @LukasReschke