#24009: get_or_create can raise an IntegrityError in race conditions
-------------------------------+--------------------------------------
Reporter: lanzz | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by lanzz):
No, I'm using PostgreSQL, and wrapping each `get_or_create` in an
individual transaction context will again make `get_or_create` worthless
by requiring at least as much boilerplate around it as it would take to
implement the get-or-create logic myself without using `get_or_create`.
--
Ticket URL: <https://code.djangoproject.com/ticket/24009#comment:2>
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/063.5a6bff2592ea4b19d18e85a881fcff5d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
