#29499: Race condition in QuerySet.update_or_create()
-------------------------------------+-------------------------------------
Reporter: Michael Sanders | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: race-condition | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Accepted
Comment:
The issue is legitimate and the suggested fix makes sense; if
`update_or_create` enforces `select_for_update()` when a row exists it
should always do so.
Would you be able to submit a PR on Github with some tests. I guess this
could qualify for backports as it's a possible data loss issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/29499#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.545e248b9612dfbb21d3a0b0725b6c33%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.