> The same problem happens when:
>
> 1) Using _.DateTime(datestring)
> 2) The datestring has minus-sign as year, month, date separators.
> 3) A format is applied, like fmt="%d DE %B %Y"
>
> The following are examples when viewing a DTML Document containing :
>
>
>
>
>
>
>
>
>
> Output is
Andreas/Tino:
Thanks for your replies regarding this date and timezones issue. (Thanks
Dieter Maurer for previous opinions also)
It has been a long and tedious problem to chase and debug, here it goes
what I have narrowed so far:
Let's forget about the undelying DA, the database has nothing to
Am Sonntag, den 22.05.2005, 13:01 -0500 schrieb Felipe Barousse Boue:
> Zopistas:
>
> I am experiencing the same problem you described by Mr. Hong Yuan in his
> post a few from last March. I have Zope 2.7.4, python 2.3.4 and
> PostgreSQL 8.0 and psycopg as DB adapter.
>
> All my dates stores in
--On Sonntag, 22. Mai 2005 13:01 Uhr -0500 Felipe Barousse Boue
<[EMAIL PROTECTED]> wrote:
I have noticed that Zope, when getting the data coming from postgresql
(the date) always takes it to be at midnight in GMT time zone.
I believe it is still a huge bug the the Zope/Python date time hand
Mixing things that have timezone and things that doesn't can always be
tricky. The hard part is identifying exactly how you expect things to
behave at each step, and then making sure it does.
In this case it seems like data written to postgres is not donverted
to GMT, but stripped of the timezone,
Zopistas:
I am experiencing the same problem you described by Mr. Hong Yuan in his
post a few from last March. I have Zope 2.7.4, python 2.3.4 and
PostgreSQL 8.0 and psycopg as DB adapter.
All my dates stores in postgresql are WITHOUT timezone and my linux is
set for the "America/Mexico City" ti
