#8669: All remaining create() methods also force an insert (continuation of
r8670)
-----------------------------------------------------------------------+----
Reporter: Richard Davies <[EMAIL PROTECTED]> | Owner:
nobody
Status: new |
Milestone: 1.0
Component: Database wrapper |
Version: SVN
Resolution: |
Keywords:
Stage: Design decision needed |
Has_patch: 1
Needs_docs: 0 |
Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------------------------+----
Changes (by mtredinnick):
* needs_better_patch: => 0
* stage: Unreviewed => Design decision needed
* needs_tests: => 0
* needs_docs: => 0
Comment:
It's not clear that `add()` should do this. At some point, if you're
playing with custom set primary keys, you have to act responsibly and by
calling that method you are saying that you want to 'add' that object,
which is what happens.
The generic relations one is probably in line with the other changes, but
I'm going to think about the first two thirds of the patch a bit.
--
Ticket URL: <http://code.djangoproject.com/ticket/8669#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
