test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[1.7.x] Fixed #23974 -- Clarified wording of FileField.save/delete save parameter. 

Thanks GreenAsJade.

Backport of 1aa41dd000 from master
This commit is contained in:
Tim Graham 2014-12-08 13:15:46 -05:00
parent 4862eb6e5b
commit 6022da4f48
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/ref/models/fields.txt
View File

@ -719,8 +719,9 @@ method is used to persist that file data.
Takes two required arguments: ``name`` which is the name of the file, and
``content`` which is an object containing the file's contents. The
optional ``save`` argument controls whether or not the instance is
saved after the file has been altered. Defaults to ``True``.
optional ``save`` argument controls whether or not the model instance is
saved after the file associated with this field has been altered. Defaults to
``True``.
Note that the ``content`` argument should be an instance of
:class:`django.core.files.File`, not Python's built-in file object.
@ -745,8 +746,9 @@ Deletes the file associated with this instance and clears all attributes on
the field. Note: This method will close the file if it happens to be open when
``delete()`` is called.
The optional ``save`` argument controls whether or not the instance is saved
after the file has been deleted. Defaults to ``True``.
The optional ``save`` argument controls whether or not the model instance is
saved after the file associated with this field has been deleted. Defaults to
``True``.
Note that when a model is deleted, related files are not deleted. If you need
to cleanup orphaned files, you'll need to handle it yourself (for instance,