#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):
Just to be clear, the scenario is the following:
- you make the first API request
- the server processes this request, performs some database operations,
commits the database transaction, sends back the response
- you receive and process the response to the first request
- you make the second API request from the same thread that made the first
request
- the server cannot see the data written by the first request
You question almost looks like the answer should involve isolation levels,
specifically the SERIALIZABLE level, but if my description above is
correct that cannot explain the behavior you're describing.
--
Ticket URL: <https://code.djangoproject.com/ticket/25432#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.db49f363c386d198b3eda2fb4775227c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
