#28038: Cast regression in PostgresSQL using built-in lookups
-------------------------------------+-------------------------------------
Reporter: Peter J. Farrell | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgres postgresql | Triage Stage:
array_agg | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Peter J. Farrell):
Replying to [comment:1 Simon Charette]:
> I don't have the time to look at this right but it looks like a bug in
your code IMHO. Wouldn't using `StringAgg` be more appropriate here?
It's definitely a regression from the behavior in 1.10 and a blocker to
upgrade apps. We would have to find all the usages of `ArrayAgg` and
convert them. In this case, we haven't found any lookups work in
conjunction with `ArrayAgg` in Django 1.11 whereas they worked in 1.10.
It would have to be documented that which lookups work with `ArrayAgg` in
Django 1.11.
Plus, it much easier to iterator over the array/list of arm_types than
having to convert a delimited string into something that can be iterated
over.
--
Ticket URL: <https://code.djangoproject.com/ticket/28038#comment:2>
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/070.f09255070ed69fcd39692cf08cfc3279%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
