#15779: admin cannot edit records with value 'add' as primary key
-------------------------------------+-------------------------------------
Reporter: Marwan Alsabbagh | Owner: claudep
<marwan.alsabbagh@…> |
Type: Bug | Status: assigned
Component: contrib.admin | Version: master
Severity: Release blocker | 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 gertsteyn):
The first paragraph of the Django URL dispatcher documentation says:
"[http://www.w3.org/Provider/Style/URI Cool URIs don’t change]"...
Do we really want to change the URL structure of every Django site out
there for an extreme edge case like this?
If I use a CharField as primary key nothing stops me from using "1/change"
as key and we'll have exactly the same problem. If you insist on using a
CharField as primary key adding some validation to exclude some "reserved"
words is not to much of an ask.
--
Ticket URL: <https://code.djangoproject.com/ticket/15779#comment:21>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/103.56479ed7a5c0085d77d93d3a3d875f19%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
