#32786: Make the subquery ordering clearing optimization more selectively
-------------------------------------+-------------------------------------
Reporter: Hannes Ljungberg | Owner: Hannes
Type: | Ljungberg
Cleanup/optimization | Status: closed
Component: Database layer | Version: dev
(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
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Replying to [comment:14 anthony sottile]:
> can this change be added to the changelog? specifically this code from
django 3.2.x no longer succeeds:
>
>
https://github.com/getsentry/sentry/blob/704da8578f2dc96afdf7e26ac29fb0f2b9576269/src/sentry/api/paginator.py#L187
>
> without a deprecation period or a changelog entry I'm not certain what
this _should_ be changed to. the commit message also doesn't help me much
either
I guess is too late for the deprecation path, as per the workaround for
3.2, I believe that's described in comment 11 in this ticket:
ticket:32786#comment:11
--
Ticket URL: <https://code.djangoproject.com/ticket/32786#comment:15>
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/01070189930f2d95-7d469b01-b524-4198-9098-67368d3a714b-000000%40eu-central-1.amazonses.com.
