#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 Amin Aminian):
Replying to [comment:19 Simon Charette]:
>
> 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.
I'm sure about this problem on Timescale, and as it is an extension for
Postgres, I think it is a corner case for Postgres (or even other DBs).
I should have tried to do this regression test earlier. It is my bad,
sorry about that.
But still, I suggest to simply have old `convert_value` to prevent corner
cases for now and for the future.
--
Ticket URL: <https://code.djangoproject.com/ticket/34564#comment:20>
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/010701885c33b44f-534b07dc-3f2a-4bac-9a92-1c8c32d27591-000000%40eu-central-1.amazonses.com.
