Well, that is what repeatable read is supposed to do -- once you do a Foo.objects.all() (or whatever) query, re-running the query will give you the same result. That's why it's called repeatable read. You have to either start a new transaction to break that visibility barrier or not use repeatable read in the first place. Which actually sounds like what you should be doing as, by the sound of it, gearman does not seem to deal with that isolation level very well.
mjl
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment