#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 Tobias Kunze):
> This is not a bug!
Could you elaborate on this? As it is changed behaviour from Django 2.1
and previous versions, it's either a bug/regression, or a documentation
bug by not mentioning this changed behaviour in the release notes, in my
opinion. Up until now I've assumed that `something.related.count()` and
`something.related.all().count()` will yield the same result, and if this
is not true, it should be documented. (Or is it documented? Could you
point me at the right place to look?)
--
Ticket URL: <https://code.djangoproject.com/ticket/30325#comment:5>
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.69cba39f1c89f8031331be178117dd05%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
