Ticket #8419: option2-create-patch.diff

django/db/models/query.py

@@ -302 +302 @@
         raise self.model.MultipleObjectsReturned("get() returned more than one %s -- it returned %s! Lookup parameters were %s"
                 % (self.model._meta.object_name, num, kwargs))
 
-    def create(self, **kwargs):
+    def create(self, force_insert=False, force_update=False, **kwargs):
         """
         Creates a new object with the given kwargs, saving it to the database
         and returning the created object.
+
+        The 'force_insert' and 'force_update' parameters can be used to insist
+        that the "create" must be an SQL insert or update (or equivalent for
+        non-SQL backends), respectively. Normally, they should not be set.
         """
         obj = self.model(**kwargs)
-        obj.save()
+        obj.save(force_insert=force_insert, force_update=force_update)
         return obj
 
     def get_or_create(self, **kwargs):

docs/ref/models/querysets.txt

@@ -560 +560 @@
 
 are equivalent.
 
+Note that if you specify the primary key value of an existing object then
+``create()`` acts as a one line shorthand for updating that object.
+
+Advanced users who wish to force the ``create()`` method to perform an SQL
+``INSERT`` or an SQL ``UPDATE`` can pass the ``force_insert=True`` or
+``force_update=True`` parameters to ``create()``, just like ``save()``
+itself.
+
 ``get_or_create(**kwargs)``
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~