Author: mtredinnick
Date: 2008-08-28 20:44:15 -0500 (Thu, 28 Aug 2008)
New Revision: 8689

Modified:
   django/trunk/docs/ref/models/instances.txt
Log:
Fixed #8662 -- Fixed the documentation of Model.save() to match the real
signature so that people overriding it will use the right signature.


Modified: django/trunk/docs/ref/models/instances.txt
===================================================================
--- django/trunk/docs/ref/models/instances.txt  2008-08-29 01:44:11 UTC (rev 
8688)
+++ django/trunk/docs/ref/models/instances.txt  2008-08-29 01:44:15 UTC (rev 
8689)
@@ -31,10 +31,15 @@
 
 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
 ------------------------------
 


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to