Thanks a lot Karen, transaction was the problem. Resolved by :
connection.cursor().execute('set transaction isolation level read
committed')
Have a nice day :)
On Thu, Oct 8, 2009 at 1:52 PM, Karen Tracey wrote:
> On Thu, Oct 8, 2009 at 5:07 AM, Alexis MINEAUD wrote:
>
&g
Ok, my bad, the sequence works well, i just confused the field name...
But the problem is still there if the update is done by another actor than
Django itself.
My standalone script is daemon which poll my DB with a XX.objects.all(). If
i updated myself a row from XX, the daemon doesn't see the m
2 matches
Mail list logo