On Apr 3, 6:23 pm, Tomasz Zieliński <tomasz.zielin...@pyconsultant.eu> wrote: > I believe that this question was asked on this group a long time ago, > and the answer was that pre_delete signal was fired *before* actual > deletion occured, > but *after* objects were collected for deletion (i.e. after list of > objects that were to be deleted > was created - you can think of this list as of "deletion tree" show in > Django admin). > > Writing this, I don't know if you've observed the same problem.
It seems that way. The bottom line is that pre_delete is not helping to prevent unintended deletion. To solve this issue I've had to define my own signal and send that in my model's delete method. Mike -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
