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:
>
>> Ok, my bad, the seq
On Thu, Oct 8, 2009 at 5:07 AM, Alexis MINEAUD wrote:
> 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()
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
On Wed, Oct 7, 2009 at 7:39 PM, laligatz wrote:
>
> Hi everybody.
>
> I'm stuck on a problem with the Django ORM.
> After a basic query like select * from table where id = 1, the result
> is still the same although i've update the row in the DB.
>
> Example:
>
> >>> Tag.objects.all()
> []
>
> >>>
Hi everybody.
I'm stuck on a problem with the Django ORM.
After a basic query like select * from table where id = 1, the result
is still the same although i've update the row in the DB.
Example:
>>> Tag.objects.all()
[]
>>> tag = Tag.objects.all().get()
>>> tag
>>> tag.name = 'tag11'
>>> t
5 matches
Mail list logo
