-
Notifications
You must be signed in to change notification settings - Fork 159
Increase in queries number #288
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
Comments
Quite a large project - am I missing anything obvious trying to reproduce it below?
|
OK I can run your test case, will take a look this evening. |
From a bisect, 3.6 passes, 3.7.0 passes, 3.7.1 and above fails If I remove our What we can probably do is move the point of registration to make it restricted to subclasses of I will work up a PR to optimise this. Also FYI @ibaguio as you might be sensitive to this. |
…ener Restrict signal handler 'senders' to subclasses of `OrderedModelBase` to avoid query count regression due to `Collector.can_fast_delete` logic in `models/deletion.py fixes #288
Fixed in 3.7.3 |
…ener Restrict signal handler 'senders' to subclasses of `OrderedModelBase` to avoid query count regression due to `Collector.can_fast_delete` logic in `models/deletion.py fixes #288
There is a query-count failure in |
On closer review You will need to patch the test if you unpin your deps as query 4 is eliminated from the test:
|
After upgrading django-ordered-model from 3.6 to 3.7.2, some of my tests started failing because the number of queries went up.
Example with one test:
Nothing else changed between both run of the test beside the django-ordered-model version.
Here is the queries run with django-ordered-model 3.6:
The 3 first queries are the same in both cases but 4th and 5th are different.
The user model is NOT ordered, it is an AbstractUser and does not make any use of any of OrderedModel feature, nor does the Group model which is the base django Group model with nothing added.
The text was updated successfully, but these errors were encountered: