#27634: Refactor Query.clone _setup_query logic
-------------------------------------+-------------------------------------
Reporter: Adam Chainz | Owner: Adam
Type: | Chainz
Cleanup/optimization | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Adam Chainz):
* status: assigned => closed
* resolution: => invalid
Comment:
Actually this can't be removed as it's needed when instantiating the
`Query` after it was created with `clone(klass=UpdateQuery)`. This might
go away if we get to actually call `Query.__init__` to create clones with
different classes, after #27624.
--
Ticket URL: <https://code.djangoproject.com/ticket/27634#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.094b393f3437649e06733ca5f21bac2d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
