#2259: PK Change creates new object instead of update
---------------------------------------------+------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: reopened | Milestone: post-1.0
Component: Database wrapper | Version:
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 1 |
---------------------------------------------+------------------------------
Changes (by mtredinnick):
* milestone: 1.0 alpha => post-1.0
Comment:
Please do not change the milestone (particularly since you've already
decided to reopen a ticket that was wontfixed without a django-dev
discussion). We've already decided on the 1.0 alpha and beta features and
this is an enhancement request.
This can quite comfortably be put off until after 1.0. I'm probably +1 on
finding a way for primary keys to be updated, but the current default
behaviour should probably remain. Having a paramater to control this won't
be the end of the world, since it's not the most common use-case on the
planet (but I agree that when you need to do it, you really, really need
it).
Marking as post-1.0 for now.
--
Ticket URL: <http://code.djangoproject.com/ticket/2259#comment:13>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
