I have two models, Volume and Group. The Volume model has a foreign key to Group.
When a user deletes a Volume the post_delete signal handler sends an HTTP DELETE request (/volume) to another server process. This works great. However, when the user deletes a Group, the cascading delete also deletes all volumes in that group. That means I get lots (I'm talking <100) of post_delete signals for the Volume model and therefore lots of HTTP requests. Is there anyway to avoid this? Ideally, I'd like to send the HTTP DELETE request (/volume) when a volume is deleted, but send a different HTTP DELETE request (/group) when the group is deleted and avoid sending any volume HTTP DELETE requests. Thanks -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/47d04a7a-7f39-4d7a-ae80-e7f54d07b29c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
