Comment 9 for bug 1245775

Hi Alex,

Yes the real issue here is that the controller delete shouldn't ideally be doing a safe_delete as the exceptions it raises is expected to be bubbled up. If you look at the patch, we've been trying to separate the actual delete from backend from the safe_delete in a way that ensures that whatever exception is caught doesn't get lost.

 The exact scenario that I'm talking about here is where the store actually catches a 404 during a controller delete but since the exception isn't raised, the execution continues as if nothing went wrong and the end response received is a 200 OK which is deceiving.