Re: Psycopg Problem with Zope's strftime

On 2006-05-22 at 21:55:52 [+0200], fog-NGVKUo/i/6DYtjvyW6yDsg@xxxxxxxxxxxxxxxx 
wrote:
> On Mon, May 22, 2006 at 09:13:46PM +0200, Charlie Clark wrote:
> > > mm, problem is, it's on a production system at the moment so I would be
> > > happier fixing it before testing Psycopg2
> > 
> > Problem is recurrent - it happens wthen I call .strftime() on a DateTime
> > object in Zope and happens all the time with psycopg2.
> > 
> > Can't see anything in the log apart from something relating to tilevel in
> > line 122 of DA.py. I have just dropped a new DA using psycopg2 into my 
> > site
> > as I have over a hundred ZSQL methods which I do not wish to replace!
> 
> Can you provide me with a test case? I'll try to fix it ASAP.

Test case for the formatting problem:

Query: SELECT datetime FROM table

result = context.SQL[0]
print result.datetime.strftime('%d.%m.%Y')

Traceback (innermost last):

    * Module ZPublisher.Publish, line 100, in publish
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 40, in call_object
    * Module Shared.DC.Scripts.Bindings, line 306, in __call__
    * Module Shared.DC.Scripts.Bindings, line 343, in _bindAndExec
    * Module Products.PythonScripts.PythonScript, line 318, in _exec
    * Module None, line 3, in date
      <PythonScript at /date>
      Line 3
    * Module DateTime.DateTime, line 1448, in strftime
    * Module DateTime.DateTime, line 414, in safegmtime

TimeError: The time -1149984000.000000 is beyond the range of this Python 
implementation, running on Win32

The other error to do with _set_state seems more difficult to reproduce.

Charlie