#28197: PostgreSQL introspection's get_constraints() retrieves index fields in
arbitrary order
-------------------------------------+-------------------------------------
Reporter: Mactory | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
From the PostgreSQL docs:
The aggregate functions array_agg, json_agg, json_object_agg,
string_agg, and xmlagg, as well as similar user-defined aggregate
functions, produce meaningfully different result values depending on the
order of the input values. This ordering is unspecified by default, but
can be controlled by writing an ORDER BY clause within the aggregate call,
as shown in Section 4.2.7. Alternatively, supplying the input values from
a sorted subquery will usually work.`
--
Ticket URL: <https://code.djangoproject.com/ticket/28197#comment:3>
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/065.139ce14502197739de11727de301f4b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
