#31202: Bulk update suffers from poor performance with large numbers of models
and
columns
-------------------------------------+-------------------------------------
Reporter: Tom Forbes | Owner: Tom
Type: | Forbes
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
-------------------------------------+-------------------------------------
Comment (by jerch):
Made some progress in https://github.com/netzkolchose/django-fast-update,
which contains `fast_update` for Postgres, sqlite, MariaDB and Mysql8, as
well as `copy_update` for postgres. The package is currently alpha (though
quite complete in CI tests), would be glad to get some feedback and some
real world tests.
Some notes about the implementations - I kinda gave up on closer
integration of `fast_update` with ORM internals, this needs someone with
deeper knowledge and time to actually do it. `copy_update` is more a PoC
with additional constraints (like values' transport repr relies alot on
correct `__str__` output), imho this could be realized more straight
forward with psycopg3's superior COPY support, once django moved there.
--
Ticket URL: <https://code.djangoproject.com/ticket/31202#comment:12>
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/01070180093ffc16-3dd61977-1e67-4c21-a9c6-1de3658d1cce-000000%40eu-central-1.amazonses.com.
