#34564: returning None instead of zero in Count annotation
-------------------------------------+-------------------------------------
Reporter: Amin Aminian | Owner: Amin
| Aminian
Type: Bug | Status: assigned
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
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
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Django doesn't support TimescaleDB so any change against it is not
considered a regression from our perspective. You might have run into bugs
with TimescaleDB for all we know.
The fact you cannot reproduce against SQLite, Postgres, MySQL, or Oracle
might explain why this was not caught by the test suite in the first place
which would make more sense given how common such annotations are.
Here are my attempts at reproducing
- [https://dbfiddle.uk/eUmjoLFI Postgres]
- [https://dbfiddle.uk/XXhzrttD MySQL]
- [https://dbfiddle.uk/esgjJ2cA SQLite]
--
Ticket URL: <https://code.djangoproject.com/ticket/34564#comment:19>
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/010701885af2de66-b9e0f01c-8b77-4436-a26a-081cce96e2e4-000000%40eu-central-1.amazonses.com.
