#10576 closed (duplicate)
file lost when transaction was rollbacked
| Reported by: | liangent | Owned by: | nobody |
|---|---|---|---|
| Component: | File uploads/storage | Version: | 1.0 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
create a model with a FileField, start a transaction, delete an object of this model, although the record in database is kept, the file is lost.
i think django should delete files in FileFields only when the transaction was committed successfully.
Change History (4)
comment:1 by , 16 years ago
| milestone: | → 1.1 |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 16 years ago
| Component: | Uncategorized → File uploads/storage |
|---|
comment:3 by , 16 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
This is a duplicate of #6456
Note:
See TracTickets
for help on using tickets.
This could be tricky to organise, but I'm inclined to agree with the idea. Having the database refer to something which doesn't exist is bad. Nice catch. :-)