On Tue, Feb 12, 2013 at 3:35 PM, Aymeric Augustin <aymeric.augus...@polytechnique.org> wrote: >> Against the possible issue of non-recognition of UTC, I suggest using >> '0:00' instead of 'UTC'. > > Thanks for looking into this problem! > > I tried '0:00' instead of 'UTC', and '+03:00' instead of > 'Africa/Nairobi' with the same result. My first queries > show that conversions are performed correctly > between these two time zones. > > When I pass an invalid time zone name I get: > ORA-01882: timezone region not found
I didn't mean to suggest this as a fix to the connection dropping problem. I only meant that the final SQL should use '0:00' instead of 'UTC' to guard against databases that for whatever reason do not have a UTC time zone definition, such as the one that I found. Otherwise the query would always fail with an ORA-01882 on those databases. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
