#35551: Unique checks skipped when changing primary key
----------------------------------+------------------------------------
Reporter: Csirmaz Bendegúz | Owner: nobody
Type: Bug | Status: new
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Changes (by Sarah Boyce):
* stage: Unreviewed => Accepted
Comment:
Great catch thank you!
> I believe step 5 should never happen, since step 3 should fail with a
unique check error.
Agreed 👍 if you were to add another field to the model then you slightly
override `Dummy (1)` with whatever is in `Dummy (2)` - which is not nice.
--
Ticket URL: <https://code.djangoproject.com/ticket/35551#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701904949d4b3-90c5e263-d31e-4507-9095-b63430058c09-000000%40eu-central-1.amazonses.com.
