[Zope] Zope 2 ODBC date errors

[Jay, Dylan]

You can either use the patch I sent before or edit DateTime.py to make sure
it has the timezone included for your country. The table at the top has to
include an entry that maps what python returns as the timezone name, to the
GMT offset.

> -----Original Message-----
> From: Graham Chiu [mailto:anon_emouse@hotmail.com]
> Sent: Monday, July 26, 1999 11:30
> To: zope@zope.org
> Subject: Re: [Zope] Zope 2 ODBC date errors
> 
> 
> In article 
> <D133051DBC4AD111B90800A0C969498391D592@natasha.auslabs.lucen
> t.com>, Jay, Dylan <djay@lucent.com> writes
> >Its that damm timezone problem in zope. If the python string 
> returned as
> >your timezone is not known to zope it barfs. This problem 
> has been going on
> >for months and I feel because it is something that only 
> effects non-american
> >zope users there has not been enough effort into fixing it. 
> In fact I have
> >fixed this bug and submitted it and am disappointed that it 
> has not made
> >into the source yet as was promised. 
> >This is a show stopping bug. In certain countries any 
> application that uses
> >dates from sql where a timezone is not supplied is going to crash!!!
> 
> Is this something I can fix locally, or do I have to wait for the next
> beta?
> 
> -------
> Regards,        Graham Chiu
> gchiu<at>compkarori.co.nz
>