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

Added a cavaet to the use of get_FOO_filename() and get_FOO_url(). This 

constraint has always existed, but it's very hard to fix in the current code,
so better to work around it for now.

Refs #5619


git-svn-id: http://code.djangoproject.com/svn/django/trunk@7999 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2008-07-19 22:26:46 +00:00
parent 5141b67a19
commit e942636fbe
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/db-api.txt
View File

@ -2280,6 +2280,12 @@ For every ``FileField``, the object will have a ``get_FOO_filename()`` method,
where ``FOO`` is the name of the field. This returns the full filesystem path
to the file, according to your ``MEDIA_ROOT`` setting.
.. note::
If you are using the ``upload_to`` parameter in your ``FileField``, it is
only valid to call this method **after** saving the model when the field
has been set. Prior to saving, the value returned will not contain the
upload directory in the path.
Note that ``ImageField`` is technically a subclass of ``FileField``, so every
model with an ``ImageField`` will also get this method.
@ -2291,6 +2297,12 @@ where ``FOO`` is the name of the field. This returns the full URL to the file,
according to your ``MEDIA_URL`` setting. If the value is blank, this method
returns an empty string.
.. note::
As with ``get_FOO_filename()``, if you are using the ``upload_to``
parameter on your ``FileField``, it is only valid to call this method
**after** saving the model, otherwise an incorrect result will be
returned.
get_FOO_size()
--------------