#35551: Unique checks skipped when changing primary key
-------------------------------------+-------------------------------------
Reporter: Csirmaz Bendegúz | Owner: Csirmaz
| Bendegúz
Type: Bug | Status: assigned
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Csirmaz Bendegúz):
I have submitted a basic fix for raising a ValidationError on PK conflict.
The other issue I would like to address is the fact that Django creates a
duplicate if there's no PK conflict.
This should also resolve the race condition issue, i.e. what if an object
is created by a separate process with the same PK **after** this check
passes. An IntegrityError should be raised in that case.
--
Ticket URL: <https://code.djangoproject.com/ticket/35551#comment:8>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/010701904f18c830-f40433cb-636e-4c0f-84ef-df165f72fa82-000000%40eu-central-1.amazonses.com.
