From d22ee35ee9193e17e31125b722ac5bb9b3ac7d82 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Fri, 29 Aug 2008 01:44:15 +0000 Subject: [PATCH] Fixed #8662 -- Fixed the documentation of Model.save() to match the real signature so that people overriding it will use the right signature. git-svn-id: http://code.djangoproject.com/svn/django/trunk@8689 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/models/instances.txt | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt index 07509daa81..e96a775e5f 100644 --- a/docs/ref/models/instances.txt +++ b/docs/ref/models/instances.txt @@ -31,10 +31,15 @@ Saving objects To save an object back to the database, call ``save()``: -.. method:: Model.save([raw=False]) +.. method:: Model.save([force_insert=False, force_update=False]) Of course, there's some subtleties; see the sections below. +**New in Django development version:** The signature of the ``save()`` method +has changed from earlier versions (``force_insert`` and ``force_update`` have +been added). If you are overriding these methods, be sure to use the correct +signature. + Auto-incrementing primary keys ------------------------------