[Zope] Zope 2 ODBC date errors

[Jay, Dylan]

> -----Original Message-----
> From: Brian Lloyd [mailto:Brian@digicool.com]
> Sent: Tuesday, July 27, 1999 04:05
> To: 'Jay, Dylan'; 'Graham Chiu'; zope@zope.org
> Subject: RE: [Zope] Zope 2 ODBC date errors
> 
> 
> > 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!!!
> > 
> > Please stop being so US centric and fix this bug!!!
> 
> Jay,
> 
> Did you submit this patch to the Collector, or just to the list?
> I don't see it in the Collector anywhere, but if you'll copy it
> to me via email I can put it in there to make sure it gets
> attention.

Its in the collector as being completed 
http://www.zope.org/Collector/314/view

The not sure if the line number is still valid but the patch was:

DateTime.py replace line 664 with
except: 
try: 
t= time()
localzone = mktime(gmtime(t)) - t
localzone = int(round(-localzone/(60*60)))
if (localzone >=0):
localzonename = '+'+str(localzone)
else:
localzonename = str(localzone)
_localzone = _cache._zmap[lower('GMT'+localzonename)] 
except: _localzone=''