From: SourceForge.net <no...@so...> - 2006-07-31 00:44:02
|
Bugs item #1531468, was opened at 2006-07-31 02:44 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=1531468&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: PgResult Group: None Status: Open Resolution: None Priority: 5 Submitted By: Christoph Zwerschke (cito) Assigned to: Nobody/Anonymous (nobody) Summary: Some problems with date/time support Initial Comment: Since I am currently improving date/time support in PyGreSQL, I had a quick look how you do it in PyPgSQL. Particularly, I found no easy solution to handle the cases when datestyle is set to 'sql,european' or 'postgres,european', since the output in this format cannot be distinguished from the US variant. I saw that PyPgSQL cannot handle this case either. Probably we can only add this as a caveat to the documentation of the modules. I also observed the following minor problems with PyPgSQL : - ValueError for intervals with microseconds - negative dates (years BC) are not handled correctly - timestamps outside the Unix epoch are not handled correctly ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=1531468&group_id=16528 |