Corrected the chronograph on my time machine. ``using`` argument was added in v1.2, not v1.1. Thanks to Ramiro Morales for the report.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@12120 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
96848352f9
commit
0e0b18229f
|
@ -71,7 +71,7 @@ To save an object back to the database, call ``save()``:
|
||||||
.. versionadded:: 1.0
|
.. versionadded:: 1.0
|
||||||
The ``force_insert`` and ``force_update`` arguments were added.
|
The ``force_insert`` and ``force_update`` arguments were added.
|
||||||
|
|
||||||
.. versionadded:: 1.1
|
.. versionadded:: 1.2
|
||||||
The ``using`` argument was added.
|
The ``using`` argument was added.
|
||||||
|
|
||||||
If you want customized saving behavior, you can override this
|
If you want customized saving behavior, you can override this
|
||||||
|
@ -272,7 +272,7 @@ Deleting objects
|
||||||
|
|
||||||
.. method:: Model.delete([using=DEFAULT_DB_ALIAS])
|
.. method:: Model.delete([using=DEFAULT_DB_ALIAS])
|
||||||
|
|
||||||
.. versionadded:: 1.1
|
.. versionadded:: 1.2
|
||||||
The ``using`` argument was added.
|
The ``using`` argument was added.
|
||||||
|
|
||||||
Issues a SQL ``DELETE`` for the object. This only deletes the object
|
Issues a SQL ``DELETE`` for the object. This only deletes the object
|
||||||
|
|
Loading…
Reference in New Issue