#34894: Query.change_aliases() has several significant bugs
-------------------------------------+-------------------------------------
Reporter: Aqua Penguin | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: Query | Triage Stage:
change_aliases | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* type: Bug => Cleanup/optimization
* resolution: => needsinfo
Comment:
`Query.change_aliases()` is a private API and, as far as I'm aware, it
works fine for internal use. Can you explain what are you trying to
implement? Did you find any existing
[https://code.djangoproject.com/query?status=assigned&status=new&component=Database+layer+(models%2C+ORM)&stage=Accepted&col=id&col=summary&col=status&col=component&col=owner&col=type&col=version&desc=1&order=id
bug] that could be fix by these changes? Can you prepare failing tests
using querysets rather than testing internal tools?
> Question: The bugs has been tested on 4.2 and main, I have to do a PR on
all current versions or only on the main branch ?
Mergers will handle backports, if needed.
--
Ticket URL: <https://code.djangoproject.com/ticket/34894#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/0107018b13472761-433291ac-f92d-4829-9428-c6193784d49b-000000%40eu-central-1.amazonses.com.
