Also there is no other view that could possibly be writing to the same row.
There are 5 rows in 5 different tables that get affected showing symptoms
similar to a rollback without any exception being raised. It's really hard
to imagine all of them had concurrent writes going on at the same time
I did initially think that it might have been a concurrent write messing
with the DB but I was able to see this issue locally once where this view
was the only one being called. The objects being saved were also using
update_fields and had the correct value on them while calling save. Is
there
On Wednesday, February 26, 2014 11:58:54 PM UTC+2, tapan pandita wrote:
>
> I am using transaction.atomic as a context manager for transactions in
> django 1.6. There is a block of code which I want to be in a transaction
> which has a couple of network calls and some database writes. I am seeing
I am using transaction.atomic as a context manager for transactions in
django 1.6. There is a block of code which I want to be in a transaction
which has a couple of network calls and some database writes. I am seeing
very weird behaviour. Every once in while (maybe 1 in 20 times) I have
noticed a
4 matches
Mail list logo
