On Saturday 18 May 2013 19:49:58 Shai Berger wrote:
>
> I'm toying with a different solution now -- removing the date casting on
> Oracle too. It passed the lookup tests, now I'm running the whole suite
> (that takes a little time). After seeing that no other backend in core
> does it, and as we do set the timestamp format, I wonder if it is really
> necessary. If that works, it's a pretty solution that affects Oracle only.
>
Running over the entire Django test-suite, the only difference that is made by
removing the cast-to-date on Oracle is that now test_lookup_date_as_str
passes; so I'm very much inclined to do that.
However, I have a little problem in my testing environment: I keep getting
"ora-01882 timezone region not found" for 5 TZ-related tests. As these are
all, of course, datetime-related tests, I'd like to get them to pass. They do
pass on our CI [0], and the mailing list includes mentions of running into
related problems. What I see when I investigate is: The test specifies the
timezone as "Africa/Nairobi", which would have been fine, exceot that by the
time it gets into the SQL to be executed, it is transformed to "EAT", which
(rightfully) triggers the error.
Florian, Aymeric, or any Django/Oracle user in Kenya: How did you overcome
this?
Thanks,
Shai.
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
