#30325: Inconsistent count() behaviour on reverse relations in ManyToManyFields
with custom model manager
-------------------------------------+-------------------------------------
Reporter: Tobias Kunze | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Marten Kenbeek):
Regression caused by [changeset:"1299421cadc4fcf63585f2f88337078e43e660e0"
1299421] (#29725). `.count()` and `.exists()` on a many-to-many relation
now use the through model's base manager instead of the related model's
default manager.
--
Ticket URL: <https://code.djangoproject.com/ticket/30325#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.088c6dff0ec95901e9c44a8e2ae7d226%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
