#17332: Doing a save after primary key has changed should raise an error
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
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 lukeplant):
* stage: Unreviewed => Design decision needed
Comment:
On the basis of the discussion in the ticket, and given that this depends
on various other pieces of work which may or may not materialize or be
merged to trunk, both in terms of providing sufficient motivation for the
change and sufficient support in other parts of the framework, I'm going
to mark as DDN.
--
Ticket URL: <https://code.djangoproject.com/ticket/17332#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 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.
