#33928: Performance issues with `on_delete=models.SET_NULL` on large tables
-------------------------------------+-------------------------------------
Reporter: Renan GEHAN | Owner: Simon
Type: | Charette
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"a9be1dc5515e99ed96a2c640f5495af419c85b93" a9be1dc5]:
{{{
#!CommitTicketReference repository=""
revision="a9be1dc5515e99ed96a2c640f5495af419c85b93"
Refs #33928 -- Removed unnecessary attribute assignment on on-delete
updates.
Model instances retrieved for bulk field update purposes are not exposed
to the outside world and thus are not required to be kept update to
date.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33928#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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070182df66066b-24c1ae8d-a16c-46c9-a8ce-48cee7237c8c-000000%40eu-central-1.amazonses.com.
