#28455: Create "inplace" QuerySets to speed up certain operations
-------------------------------------+-------------------------------------
Reporter: Anssi Kääriäinen | Owner: Keryn
Type: | Knight
Cleanup/optimization | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | 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 Keryn Knight):
* owner: nobody => Keryn Knight
* status: new => assigned
Comment:
I don't think I'm stepping on anyone's toes at this juncture, but do shout
if so!
I'd accidentally been wading into similar waters when I stumbled across
this ticket, which has ended up at roughly the same place/conclusions, and
I have a rough sketch based on the prior branches for an MVP to resume
discussion on this. I'll tidy up what I have, try and gather some simple
benchmarks, and throw it into the PR queue for sanity checking.
I guarantee there's more nuance to this than I've anticipated so far, but
we've got to restart somewhere, right? If it works out, all the better :)
--
Ticket URL: <https://code.djangoproject.com/ticket/28455#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/066.2e561b84b5871b94ca82ef1a6068fc02%40djangoproject.com.