Module should use the core Batch API to avoid timing out
| Project: | Delete all |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Hi,
1) Does the node_delete() method automatically delete also all content of CCK fields in the given content type?
2) I have a content type with over 130k entries, on a production site, that I need to discard. There are many CCK fields in this content type that also must be deleted. I assume I will have to keep reloading the expiring page many times before all nodes in that content type are deleted. Is that the way to do it?
Thanks for working on this - this actually seems like something that should be a part of Drupal core one day. The logical thing for me to achieve the above would be going to /admin/content/types and deleting the content type - with all its node and CCK data. Or in /admin/content/node/overview, passing the work to cron in cases of mass deletions.
#1
This is now an old issue, but in case anyone is asking the same question I have successfully used this module (in normal mode) to delete 70,000 CCK nodes, each containing over 50 fields, plus related taxonomy terms, url aliases etc.
I found that the module deleted about 1000 nodes at a time before crashing. So effectively this meant going back and pressing the delete button many times. This was tedious but easier than doing this with views bulk operations, or deleting the content type and recreating each field, or trying to delete the records directly through the database.
Ideally this module would incorporate a batch delete function so it could cope better with very large numbers of nodes- which is where it is most useful/ essential.
I agree that this as a crucial module and should ultimately be in core. Thanks for maintaining it
#2
Altering the title slightly to what I think the issue is. Correct me if I'm wrong. Will try it out this afternoon.