#33767: Ordering by F-expression resolving to a number returns wrong results
-------------------------------------+-------------------------------------
Reporter: Florian Apolloner | Owner: Florian
| Apolloner
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Florian Apolloner):
* status: assigned => closed
* resolution: => duplicate
Comment:
Replying to [comment:7 Simon Charette]:
> yeah I think we should merge the two tickets together.
Ok, I am closing this one since the other includes more context (#33768)
> Ultimately the issue covered by
[https://github.com/django/django/pull/15687 the submitted PR] is to make
sure that we properly order by selected references when possible?
Yes; while trying to fix it I looked for other problems we might have in
that area which led to the current findings.
--
Ticket URL: <https://code.djangoproject.com/ticket/33767#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018180307919-b84f1ae5-4885-43ab-93f6-aaf6e55d9967-000000%40eu-central-1.amazonses.com.
