Fixed #6456 - Excised FileField file deletion to avoid data loss. Thanks to durdinator for the report.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15321 bcc190cf-cafb-0310-a4f2-bffc1f526a37

1 files changed, 14 insertions, 0 deletions

diff --git a/docs/releases/1.3.txt b/docs/releases/1.3.txt
index 89e8b58585..1ca89380f7 100644
--- a/docs/releases/1.3.txt
+++ b/docs/releases/1.3.txt
@@ -261,6 +261,20 @@ requests. These include:
 Backwards-incompatible changes in 1.3
 =====================================
 
+FileField no longer deletes 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).
+
 PasswordInput default rendering behavior
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~