-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache not invalidated for query using Case annotation for ManyToManyField #259
base: master
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 9876302138Details
💛 - Coveralls |
thx! |
You're welcome! Although it looks like my test isn't failing here...let me look into why that is, it was failing locally... |
cc444ae
to
89c437e
Compare
Got it, the test was not being imported in |
@Andrew-Chen-Wang would you be able to re-run the workflow, I think this should fail now. Thanks. |
Thanks, that's failing now. Hopefully someone can figure out why, sorry I can't be more help. |
FWIW, running |
That's great, thank you! I had no idea that flag existed. Looks like the I assumed all tables were captured by cachalot, the comment below from the code was a surprise. # Tables may be overlooked by the regular checks as not all expressions are handled yet. It would be useful to have a list of all the known expressions which aren't handled in the documentation. I'll leave this PR open for now as an example of one of the overlooked tables cases. Thanks again for your help. |
@danlamanna I see you've already raised everything I asked about in #265 and #266, thanks. |
Description
This PR contains a failing test which shows a bug when filtering on annotations of a ManyToManyField. The cache isn't invalidated but I'm not sure why. I've added it as PR so hopefully someone more knowledgable of the codebase can diagnose what's going on.
Rationale
This looks like a bug - caches on the tables on which the query filters on should be invalidated. See issue #255.