#29538: Query Expression in ordering of a related object fails
-------------------------------------+-------------------------------------
Reporter: wilhelmhb | Owner: Eduardo
| Rivas
Type: Bug | Status: closed
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: ordering, query | Triage Stage: Ready for
expression, related object | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by a-p-f):
Sorry for my ignorance, but is there a simple way for users to see, from
this page, which minor versions of Django have received this patch? I
followed the link to the github commit page, and from what I could tell
there, the fix was implemented in 4.1. That doesn't tell me, however, if
the commit was cherry-picked into any other branches.
At first I had assumed that since 3.2 was the latest LTS release, it would
receive this fix. I upgraded to 3.2.18, though, and this bug isn't fixed.
Looking closer at Django's docs, I see that 3.2 is only in extended
support, and this bug does not qualify for extended support. Fair enough.
I just think it would help developers to make it clear which of the
current versions have received a given fix.
--
Ticket URL: <https://code.djangoproject.com/ticket/29538#comment:16>
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/0107018728c35509-694879b3-1d05-4a09-9277-c404277deb39-000000%40eu-central-1.amazonses.com.
