Don't cache values()
and values_list()
#115
Closed
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.
This extends PR #113 with two additional test methods:
test_no_cache_values
andtest_no_cache_values_list
. These methods provide an assertion of the behaviour indicated by the documentation regarding calls to.values()
and.values_list()
. That is, that queries involving these calls are not cached.This PR was written as a prefix to bug report #116 to do with Django 1.9.
Note: the travis tests are failing because of an unpinned version install on
flake8
. If you bump travis to rerunmaster
, it will fail for the same reason due to additional checks introduced inflake8
since travis was last run onmaster
.