From: SourceForge.net <no...@so...> - 2006-10-24 04:51:29
|
Patches item #1583325, was opened at 2006-10-24 04:48 Message generated for change (Comment added) made by davecole You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=1583325&group_id=16528 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Cole (davecole) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect handling of TIMESTAMP columns Initial Comment: The 2.5.1 module incorrectly applies the timezone offset to TIMESTAMP columns. I get correct results querying TIMESTAMP columns using pqsl but pyPgSQL seems to be double applying the timezone offset. The attached patch Works For Me (TM) by only doing the localtime() conversion for TIMESTAMP WITH TIME ZONE columns. ---------------------------------------------------------------------- >Comment By: Dave Cole (davecole) Date: 2006-10-24 04:51 Message: Logged In: YES user_id=28658 And here is the small test program I used to see the before and after behaviour. $ python test-timestamp DATABASE-NAME ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=1583325&group_id=16528 |