#28228: changing a primary key and saving results in a new object rather than
renaming the existing object.
-------------------------------------+-------------------------------------
Reporter: Chris Withers | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
I found [https://groups.google.com/d/topic/django-
developers/sCjjx6NmMw4/discussion an old proposal to deprecate the current
behavior]. Perhaps that conversation could be resumed -- I don't think
there's been any other recent discussion about it on the mailing list.
--
Ticket URL: <https://code.djangoproject.com/ticket/28228#comment:4>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.c28995779f436b9d8f2effa8cefababb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
