#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: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
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 Chris Withers):
Documenting buggy behaviour doesn't make it any less buggy. How are you
supposed to handle renames?
(Normal relational database behaviour is that change of the primary key
results in a change to the primary key, with cascading if so configured,
or an IntegrityError if not and there are foreign keys referring to this).
--
Ticket URL: <https://code.djangoproject.com/ticket/28228#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 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/064.bb7fca0bb8dd85f5d40e670c77695bce%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
