@TheBeardedTemplar,
I'm happy this solves the problem, but its more like a workaround, I'm
interested to understand how this raise condition is achieved. ;)
One thing that I was thinking that can cause this raise condition is that
by default Django emulates CASCADE DELETE behavior on ForeignKeys
HI guis,
I need to mention one point that works well for me.
If you check blob existence with:
hasattr(widget, 'blob')
then django responds False in the case Blob Does Not exist an True
otherwise.
At the same time DB request is performed but DoesNotExist exception is not
raised.
On Fri, Aug 12
On Friday, August 12, 2016 at 1:19:17 PM UTC-6, Todor Velichkov wrote:
>
> Some more code will be helpful, for example the model structure, how do
> you define the the `ForeignKey`? How do you subscribe for the signal?
> You are saying that with sleep(1) the code works fine, is this mean that
>
Some more code will be helpful, for example the model structure, how do you
define the the `ForeignKey`? How do you subscribe for the signal?
You are saying that with sleep(1) the code works fine, is this mean that
you can reproduce the problem at any time?
However test it without fetching the bl
4 matches
Mail list logo
