#18413 closed Cleanup/optimization (fixed)
documentation on delete() should mention that associated file or image is not deleted
| Reported by: | Kenneth Gonsalves | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.4 |
| Severity: | Normal | Keywords: | delete FileField |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
When a model contains an image or file field, deleting an instance will not delete the file/image on disk. The user has to do this manually. The relevant section in the 1.3 release notes should be added to the documentation
Attachments (1)
Change History (6)
comment:1 by , 13 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
by , 13 years ago
| Attachment: | 18413.diff added |
|---|
comment:2 by , 13 years ago
| Has patch: | set |
|---|
comment:3 by , 13 years ago
This seems to be pretty much copied from the 1.3 release notes - which is fine, but I don't think that you need to mention the FileField.delete() method specifically in this new context. It would probably be enough to just say something along the lines of: "Note that when a model is deleted, related files will remain on disk."
comment:4 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Yes, this could go either in the documentation of
Model.delete()or in the documentation ofFileField.The commit that introduced this behavior is [00e7a571c5].