#25432: Django ORM race condition
-------------------------------------+-------------------------------------
Reporter: yuvadm | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
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 aaugustin):
Actually making both requests from the same thread doesn't matter because
they may be handled by different processes on the server.
Even at the SERIALIZABLE isolation level, the database is allowed to
serialize transactions made on different connections in any consistent
order.
I think this is part of the consistency model of multi-processes databases
servers, which are distributed systems even if they run on one server
I don't think there's anything specific to Django here. You should be able
to reproduce this behavior with plain WSGI & pyscopg2.
--
Ticket URL: <https://code.djangoproject.com/ticket/25432#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 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/064.b258d7604fa3996eaec8e9ced7dcc9b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
