#36489: OneToOneField + concurrent get_or_create results in wrong object in
field
cache
-------------------------------------+-------------------------------------
Reporter: Brian Atkinson | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sina Chaichi):
I opened new PR for this issue:
https://github.com/django/django/pull/19890
This patch adds conditional reverse OneToOne cache clearing to fix stale
instances left during concurrent get_or_create()/update_or_create() races.
It also includes regression tests (get_or_create, update_or_create, with
defaults) and release notes.
--
Ticket URL: <https://code.djangoproject.com/ticket/36489#comment:19>
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/01070199720ed193-fe4a879e-b574-4242-a177-f7d8e80deaf2-000000%40eu-central-1.amazonses.com.
