[Pypgsql-devel] [ pypgsql-Bugs-1199311 ] timestamp/timezone handling error in CVS head (OK in 2.4.0)

[SourceForge.net <no...@so...>]

Bugs item #1199311, was opened at 2005-05-10 14:54
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116528&aid=1199311&group_id=16528

Category: PgSQL
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Damon Hart (damonhart)
Assigned to: Nobody/Anonymous (nobody)
Summary: timestamp/timezone handling error in CVS head (OK in 2.4.0)

Initial Comment:
Please find attached a transcript of a psql session
creating a trivial test table and inserting/retrieving
one timestamp. Also attached are transcripts of two
interactive Python sessions using PgSQL, one from CVS
head (as of 2005-05-04) the other the 2.4.0 release
(installed via RPM.)

The timestamp retrieved with 2.4.0 looks OK, but the
one retrieved using CVS head is four hours ahead. I'll
speculate that this is a timezone issue, since the
machine's timezone (both client and server) is
America/New_York and is currently 4 hours behind UTC.



Environment:

all software on one machine, Fedora Core 3 with
PostgreSQL updated to 8.0.2 via PGDG RPMs.
egenix-mx-base-2.0.6-py2.3_ucs4_1 from RPM for the
datetime handling. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116528&aid=1199311&group_id=16528