#29118: QuerySet.order_by(Exists(...)) crashes
-------------------------------------+-------------------------------------
Reporter: Raphael Gaschignard | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"bf26f66029bca94b007a2452679ac004598364a6" bf26f66]:
{{{
#!CommitTicketReference repository=""
revision="bf26f66029bca94b007a2452679ac004598364a6"
Fixed #29118 -- Fixed crash with QuerySet.order_by(Exists(...)).
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29118#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/062.a42925b95ecdc1e6a34e50b5b8eac771%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.