#17332: Doing a save after primary key has changed should raise an error
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.3
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage: Design
Keywords: | decision needed
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* status: new => closed
* resolution: => wontfix
Comment:
I am closing this ticket. Better way forward is having a model
subclass/mixin which does automatic primary key updates for you (or at
least raises an error on changed primary key). This is backwards
compatible, explicit, and does not add any overhead to those who do not
need this feature.
--
Ticket URL: <https://code.djangoproject.com/ticket/17332#comment:3>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
