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
'set transaction isolation level read committed' did not fix the
problem, however 'set autocommit=1' did give the daemon realtime
visibility into what the web interface was doing.
Thanks for you help and for giving me something exciting to play with
over the weekend :)
On Jun 26, 2:52 am, Karen Tracey <kmtra...@gmail.com> wrote:
> On Thu, Jun 25, 2009 at 4:48 PM, afrobeard <afrobe...@gmail.com> 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:
> > 2 rs = Inqueue.objects.filter(processed = 0).order_by('-timestamp')
> > 3 for item in rs:
> > 4.1 processitem(item)
> > 4.2 item.delete()
> > 5 sleep
>
> What database are you using? This sounds more like a transaction isolation
> problem than a caching issue.
>
> Karen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
