#36299: ORM Regressions in Django 5.2
-------------------------------------+-------------------------------------
Reporter: OutOfFocus4 | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* owner: (none) => Simon Charette
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
* status: new => assigned
Comment:
Regression in #28900 (65ad4ade74dc9208b9d686a451cd6045df0c9c3a)
Thanks for the detailed report.
> The first issue I noticed is that calling alias on after values_list
adds the aliased value to the result set. I believe the root of this error
is in django/db/models/sql/query.py lines 1224 and 1225:
> ...
> This code adds the alias to selected regardless of the value of the
select parameter.
That's effectively the origin of the problem, thanks for investigating.
Currently looking into the second one with `select_for_update`.
--
Ticket URL: <https://code.djangoproject.com/ticket/36299#comment:2>
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 visit
https://groups.google.com/d/msgid/django-updates/01070196011793f5-37cde3a5-361e-4918-ad28-49850b274eab-000000%40eu-central-1.amazonses.com.
