I'm using MySQL 5.1.33
I shifted the db engine to MyISAM from INNODB and everything worked
like a charm. Then I switched it back to INNODB to test the pythonic
workarounds from
http://groups.google.com/group/django-users/browse_thread/thread/e25cec400598c06d/55fa3724d2754013?#55fa3724d2754013
On Thu, Jun 25, 2009 at 4:48 PM, afrobeard wrote:
>
> Thanks for the reply Alex, however I beleive I might have
> miscommunicated the problem a big. The actual format of the daemon is
> somewhat like this:-
>
> 1while True:
> 2rs = Inqueue.objects.filter(processed =
Which backend are you using? If you happen to be using MySQL with InnoDB,
and you haven't altered the default settings you are probably using an
isolation level of REPEATABLE-READ.
You can read more about that setting here
Thanks for the reply Alex, however I beleive I might have
miscommunicated the problem a big. The actual format of the daemon is
somewhat like this:-
1while True:
2rs = Inqueue.objects.filter(processed = 0).order_by('-timestamp')
3for item in rs:
4.1 processitem(item)
4.2
On Thu, Jun 25, 2009 at 3:31 PM, afrobeard wrote:
>
> I have a problem where I'm using Django, specifically the ORM in a non
> web based daemon script to process some data from a site, by setting
> the environment variables respectively so that it knows where the
> settings
I have a problem where I'm using Django, specifically the ORM in a non
web based daemon script to process some data from a site, by setting
the environment variables respectively so that it knows where the
settings module is, etc
I'm running the following query:-
6 matches
Mail list logo