Thanks a lot, didn't thought about that in the first place :)

yuri kirjoitti:
> Yip, we had the same problem, it's to do with the time change that
> happened 2 days ago. To cut a long story short, set the timezone in
> your settings file to TIME_ZONE = ""
> Django will then use the timezone returned by windows.
> 
> The problem is that in django.conf.settings.py, line 64, it sets the TZ
> variable. The timezone it tries to set is from the postgres database,
> i.e. the link given in the settings file. These however are not valid
> for mysql, so mysql resets it to GMT. So, the thread reloads, thinking
> that the timestamp for a file has changed. And it keeps doing it over
> and over.
> 
> 
> 
> 


--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to