#36213: Document that QuerySet.update can execute two separate SQL queries when
using MySQL
-------------------------------------+-------------------------------------
Reporter: Babak | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: dev
Severity: Normal | Resolution:
Keywords: mysql self-select | Triage Stage: Accepted
race-condition |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
> This seems like it's the same thing:
https://www.reddit.com/r/django/comments/1ixb489/high_memory_usage_on_delete/
Unless they are making use of `on_delete=models.SET_NULL` or `models.SET`
which make use of `update` it's not the same thing.
--
Ticket URL: <https://code.djangoproject.com/ticket/36213#comment:6>
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/010701953d8205c3-90ee12cf-41be-418c-a4a2-b190b2cce787-000000%40eu-central-1.amazonses.com.
