#30628: order_by() on union() querysets results with wrong ordering when the
same
field type is presented multiple times.
-------------------------------------+-------------------------------------
Reporter: Julien Enselme | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"df2c4952df6d93c575fb8a3c853dc9d4c2449f36" df2c495]:
{{{#!CommitTicketReference repository=""
revision="df2c4952df6d93c575fb8a3c853dc9d4c2449f36"
Fixed #36173 -- Stabilized identity of Concat with an explicit
output_field.
When Expression.__init__() overrides make use of *args, **kwargs
captures their argument values are respectively bound as a tuple and
dict instances. These composite values might themselves contain values
that require special identity treatments such as Concat(output_field)
as it's a Field instance.
Refs #30628 which introduced bound Field differentiation but lacked
argument captures handling.
Thanks erchenstein for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30628#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701950a356be6-8c4be96f-f4ef-44e1-b1e4-737763765911-000000%40eu-central-1.amazonses.com.
