Ticket #15588: filefield_doc.diff

File filefield_doc.diff, 1.6 KB (added by Philip Neustrom <philipn@…>, 4 years ago)
  • docs/releases/1.3.txt

     
    359359mechanism mentioned above. This is backwards-incompatible for any
    360360users relying on the prior ability to insert arbitrary lookups.
    361361
    362 FileField no longer deletes files
    363 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     362Deleting a model doesn't delete associated files
     363~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    364364
    365365In earlier Django versions, when a model instance containing a
    366366:class:`~django.db.models.FileField` was deleted,
    367367:class:`~django.db.models.FileField` took it upon itself to also delete the
    368368file from the backend storage. This opened the door to several data-loss
    369369scenarios, including rolled-back transactions and fields on different models
    370 referencing the same file. In Django 1.3, :class:`~django.db.models.FileField`
    371 will never delete files from the backend storage. If you need cleanup of
    372 orphaned files, you'll need to handle it yourself (for instance, with a custom
    373 management command that can be run manually or scheduled to run periodically
    374 via e.g. cron).
     370referencing the same file. In Django 1.3, when a model is deleted the
     371:class:`~django.db.models.FileField`'s
     372:func:`~django.db.models.FileField.delete` method won't be called.  If you
     373need cleanup of orphaned files, you'll need to handle it yourself (for
     374instance, with a custom management command that can be run manually or
     375scheduled to run periodically via e.g. cron).
    375376
    376377PasswordInput default rendering behavior
    377378~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Back to Top