#33973: Performance regression when moving from 3.1 to 3.2
-------------------------------------+-------------------------------------
Reporter: Marc Parizeau | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 3.2
Severity: Normal | Resolution:
Keywords: performance | Triage Stage:
regression | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
> Did something major happen in SQL generation from 3.1 to 3.2?
Each version of Django includes many bugfixes and new ORM features that
affect the generated SQL.
Can you reproduce the same regression on Django 4.1 and the current `main`
branch? Can you
[https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
tickets/#bisecting-a-regression bisect a regression]?
--
Ticket URL: <https://code.djangoproject.com/ticket/33973#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070182fa19a793-bb97ba16-530b-4a6a-8221-fd783a0b2060-000000%40eu-central-1.amazonses.com.
