On Thu, Oct 8, 2009 at 5:07 AM, Alexis MINEAUD <lalig...@gmail.com> 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(). If > i updated myself a row from XX, the daemon doesn't see the modification > until i relaunch it. > > Even a Tag.objects.get(id = 1) for example ignore the update. > > Is there a way to force the query again ? > > Django does issue the query again, if you are getting the same result it is because that is what the database is returning. You don't mention what database you are using. When I have seen this before it has always been due to MySQL/InnoDB's default transaction isolation level of repeatable read. If that is the DB you are using you might want to read this thread: http://groups.google.com/group/django-users/browse_thread/thread/e25cec400598c06d/ If you are using a different DB you might want to investigate its trasnaction isolation level handling. 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 -~----------~----~----~----~------~----~------~--~---
