#2259: Primary keys should be readonly by default in admin
-------------------------------+--------------------------------------
Reporter: ed@… | Owner: Jason Hall
Type: Bug | Status: assigned
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
-------------------------------+--------------------------------------
Comment (by Jason Hall):
Is this something that should be handled here, or in a separate ticket? I
was under the impression that this ticket is focused on making primary
keys read-only in the admin when editing existing objects, mainly to avoid
the silent insert/overwrite issues that can happen when PKs are editable.
I wouldn't mind looking into the behavior you're describing, but I'd
prefer to avoid investing time only to have it re-scoped or restructured
later. Just want to make sure we're aligned on whether that should be part
of this ticket or tracked separately.
--
Ticket URL: <https://code.djangoproject.com/ticket/2259#comment:55>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070198511ca7bb-730da62a-48a8-42fe-b6ac-35a014bacf76-000000%40eu-central-1.amazonses.com.
