Opened 6 years ago
Closed 6 years ago
#29651 closed Cleanup/optimization (duplicate)
MemoryError while deleting object with huge amount of related objects
| Reported by: | Sven R. Kunze | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.admin | Version: | 2.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
It seems like Django admin is loading all related objects into memory while deleting via admin interface.
Can we make deleting related objects iteratively (applying signals etc.)?
SO question on this topic I found so far:
https://stackoverflow.com/questions/31477723/how-to-prevent-django-from-loading-objects-in-memory-when-using-delete
Related ticket #10919
Change History (1)
comment:1 by , 6 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I'd consider this a duplicate of #10919. Even if the solution ends up different than that ticket's title, the underlying issue is the same, I think. If you have a solution to offer that doesn't address the related ticket, feel free to reopen.