#15779: admin cannot edit records with value 'add' as primary key
-------------------------------------+-------------------------------------
Reporter: Marwan | Owner: nobody
Alsabbagh <marwan.alsabbagh@…> | Status: new
Type: Bug | Component: contrib.admin
Milestone: | Severity: Normal
Version: 1.3 | Keywords:
Resolution: | Has patch: 0
Triage Stage: Design | Needs tests: 0
decision needed |
Needs documentation: 0 |
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by julien):
* needs_better_patch: => 0
* stage: Unreviewed => Design decision needed
* needs_tests: => 0
* needs_docs: => 0
Comment:
Yes this is an issue. Now we need to find the proper way to fix it.
One (naive) idea is to make the "add/" url configurable, perhaps using a
setting. But still, this wouldn't be ideal as a conflict would still
potentially exist if whatever value you give to that setting is then used
as a primary key.
Really, the url schema for the admin is slightly flawed here. Down the
track we might want to redesign it to avoid any sort of conflict -- but
that would likely be heavily backwards incompatible.
--
Ticket URL: <http://code.djangoproject.com/ticket/15779#comment:1>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
