#36526: bulk_update uses more memory than expected
-------------------------------------+-------------------------------------
Reporter: Anže Pečar | Owner: Jason
| Hall
Type: Uncategorized | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
I feel like we should likely close this one in favor of #31202
particularly because the proposed solution of
[https://github.com/django/django/pull/19677#pullrequestreview-3059926789
of batching the resolving of the expression] while the transaction is
opened is likely going to cause more harm than good until the query
resolving and compilation of the batches is made faster.
--
Ticket URL: <https://code.djangoproject.com/ticket/36526#comment:7>
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/010701984ec70a65-d261c879-4ff1-4fab-bc54-5133c144b5f1-000000%40eu-central-1.amazonses.com.
