Browse files

[1.3.X] Fixes #15588 -- 1.3 release documentation for FileField no lo…

…nger deleting files unclear. Thanks for the patch, Philip Neustrom.

Backport of r16205 from trunk.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent fda65ff commit 4cb2b53c222a8b02941d7bd32f012e62c1acd94f @SmileyChris SmileyChris committed May 10, 2011
Showing with 8 additions and 7 deletions.
  1. +8 −7 docs/releases/1.3.txt
15 docs/releases/1.3.txt
@@ -358,19 +358,20 @@ issues`_ reported to us, however, query string lookup arguments in the
admin must be for fields or relations specified in ``list_filter`` or
-FileField no longer deletes files
+Deleting a model doesn't delete associated files
In earlier Django versions, when a model instance containing a
:class:`~django.db.models.FileField` was deleted,
:class:`~django.db.models.FileField` took it upon itself to also delete the
file from the backend storage. This opened the door to several data-loss
scenarios, including rolled-back transactions and fields on different models
-referencing the same file. In Django 1.3, :class:`~django.db.models.FileField`
-will never delete files from the backend storage. If you need cleanup of
-orphaned files, you'll need to handle it yourself (for instance, with a custom
-management command that can be run manually or scheduled to run periodically
-via e.g. cron).
+referencing the same file. In Django 1.3, when a model is deleted the
+:func:`~django.db.models.FileField.delete` method won't be called. If you
+need cleanup of orphaned files, you'll need to handle it yourself (for
+instance, with a custom management command that can be run manually or
+scheduled to run periodically via e.g. cron).
PasswordInput default rendering behavior

0 comments on commit 4cb2b53

Please sign in to comment.