#34564: returning None instead of zero in Count annotation
-------------------------------------+-------------------------------------
Reporter: Amin Aminian | Owner: Amin
| Aminian
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: count, orm, | Triage Stage: Accepted
annotate |
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: assigned => closed
* resolution: => invalid
Comment:
Unfortunately this was not even demonstrated to be a corner case for
Postgres, if it was the case we'd certainly accept a patch for it.
We can't keep code around that we can't test for regression against I'm
afraid.
If someone is able to write a test demonstrating that `Count` can return
`NULL` values from modern SQL standard or against any supported database
backend that might diverge from the standard (Postgres, SQLite, MySQL,
Oracle) we can re-open this ticket but in the mean time this ticket
doesn't seem actionable.
--
Ticket URL: <https://code.djangoproject.com/ticket/34564#comment:21>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018865af8164-78507d86-5b4d-4c11-aa1f-600adb7c9405-000000%40eu-central-1.amazonses.com.
