On Tue, Oct 12, 2010 at 11:42 PM, Stodge <[email protected]> wrote: > Short of creating my own custom FileField class, is there anyway to > pass an optional "delete" flag to a custom file system storage? I have > a case where I want to delete the FileField record, but not the file.
This was discussed at DjangoCon; this behavior of FileField could be legitimately be considered a bug, since there's no guarantee that two FileFields aren't pointing to the same file, or (as in your case) that deleting a FileField record actually means that the underlying file should be deleted. Deleting data by default is an inherently dangerous practice, and it probably shouldn't be the default behavior of file fields. I haven't gone searching the ticket database to see if this has been raised before, but if it hasn't, this issue should be logged and looked at. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
