[Zope-DB] DCOracle2 1.3b resolving Oracle Dates one day behind?

Chris Sorisio chrissorisio at peaktechnical.com
Thu May 13 10:08:00 EDT 2004


When I switch back to DCOracle2 1.2, the behavior is as expected and 
OracleDates are resolving properly.

Chris Sorisio wrote:

> Heya folks,
>
> I recently came across a puzzling problem while moving some scripts to 
> a new server.  Here's an example:
>
> >>> print track[1]
> [1348191L, OracleDate("2003-09-03 00:00:00"), 130955L, None, 14515L, 
> None, 'ZRWS', 'Lori - assistant - Richard out til next week', 
> OracleDate("2003-09-03 00:00:00"), 'ZLRH', OracleDate("2004-05-12 
> 00:00:00"), 'ZRWS', '0204PM', 4L, None, 1L]
> >>> e = track[1][10]
> >>> print e
> 2004-05-12 00:00:00
> >>> import time
> >>> print time.strftime("%Y-%m-%d", time.localtime(int(e)))
> 2004-05-11
> >>> print int(e)
> 1084316400
>
> Any ideas what could be causing this?





More information about the Zope-DB mailing list