#36638: The default for ArrayAgg should be an empty list rather than None
-------------------------------------+-------------------------------------
Reporter: Markus Amalthea | Owner: (none)
Magnuson |
Type: Uncategorized | Status: closed
Component: contrib.postgres | Version: 5.2
Severity: Normal | Resolution: invalid
Keywords: ArrayAgg | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* component: Uncategorized => contrib.postgres
* keywords: => ArrayAgg
* resolution: => invalid
* status: new => closed
Comment:
See #10929 and fee87345967b3d917b618533585076cbfa43451b: Django used to do
that, but deprecated it and removed it in 5.0, due to it being
inconsistent with other aggregates. (The inconsistency was a compromise
given the lack of `default` at the time.)
You can use `default=Value([])` if you prefer. See
https://docs.djangoproject.com/en/5.2/releases/4.0/#id2.
--
Ticket URL: <https://code.djangoproject.com/ticket/36638#comment:1>
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 visit
https://groups.google.com/d/msgid/django-updates/01070199aab54d6f-19425459-ff61-4234-a433-2ee251d09c9e-000000%40eu-central-1.amazonses.com.
