Re: post_delete and determining if a related object has been deleted

> Den 28/07/2015 kl. 14.36 skrev Stefan Schindler : > >> This makes no sense to me. You want to delete an Item or Order but >> then immediately create a new one? > > My actual goal is this: Whenever an Item object itself is deleted, I > want to create a LogEntry object

Re: post_delete and determining if a related object has been deleted

> This makes no sense to me. You want to delete an Item or Order but > then immediately create a new one? My actual goal is this: Whenever an Item object itself is deleted, I want to create a LogEntry object attached to the item's order. If an order is deleted however, I don't want to do

Re: post_delete and determining if a related object has been deleted

> Den 28/07/2015 kl. 09.37 skrev Stefan Schindler : > > If the Order object itself is deleted, all post_delete handlers of all > related objects are fired, including Item. Item however stores a new > object with a relation to the *deleted Order* object, which will > result in a

post_delete and determining if a related object has been deleted

Hey guys, the post_delete signal is fired before the PK field of the deleted and all related objects is set to None. This leads to the situation that one can't determine if a related object has been deleted in a post_delete handler. Here's an example: "Order", "Item" and "LogEntry" are the