Implemented qinspect as a context manager. #29
Conversation
This file contains 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.
I adore django-queryinspect, but it can't be used in things like management commands or other non-request contexts (e.g. celery tasks), since it's a middleware.
So I implemented the same functionality as a context manager. It worked great, so I figured I'd contribute it back to the original project.
I also fixed a small bug in
QueryInspectMiddleware.check_stddev_limit()was clearly intended to be a classmethod, but the decorator was missing. I needed it to be a classmethod to make the context manager work, so I fixed that.