#32711: MySQL performance regression in
forms.models.apply_limit_choices_to_to_formfield
------------------------------------+--------------------------------------
Reporter: Thomas Achtemichuk | Owner: nobody
Type: Uncategorized | Status: closed
Component: Forms | Version: 3.2
Severity: Normal | Resolution: worksforme
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Comment (by Thomas Achtemichuk):
Thanks for following up Mariusz & Simon.
I agree that this smacks of typically poor MySQL subquery optimization,
which is one of the reasons we're planning on migrating to PostgreSQL in
the near future. In the meantime, I've monkeypatched in the
`apply_limit_choices_to_to_formfield` from 3.1 which is doing the trick
for us. And as 5.7 is quickly approaching EOL, probably not worth any more
time/attention to the issue we're seeing.
Simon, we're on MySQL 5.7.25, so a few minor versions back from the
current GA release of 5.7.34 (or 5.7.33, available on RDS). Swapping the
order of the condition doesn't seem to have any effect.
--
Ticket URL: <https://code.djangoproject.com/ticket/32711#comment:3>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/065.b38d54d88d55ecd3acb1a1bf956de659%40djangoproject.com.
