From: SourceForge.net <no...@so...> - 2005-10-14 05:04:45
|
Bugs item #1325835, was opened at 2005-10-13 09:57 Message generated for change (Comment added) made by ballie01 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=1325835&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: PgSQL Group: None Status: Open Resolution: None >Priority: 5 Submitted By: Harald Armin Massa (ghum) >Assigned to: Billy G. Allie (ballie01) Summary: PyPGSQl crashes Python on specific dates Initial Comment: cs=cn.cursor() cs.execute("select '1932-01-01 00:00'::timestamp") cs.fetchone() leads to a total crash of Python ("invalid memory access"), not a mere exception, but a hard crash. to reproduce: cn must be a conneciton ... Harald ---------------------------------------------------------------------- >Comment By: Billy G. Allie (ballie01) Date: 2005-10-14 01:04 Message: Logged In: YES user_id=8500 I'm not able to reproduce the error: >>> cn = PgSQL.connect(database='issueLog', password='********) >>> cur = cn.cursor() >>> cur.execute("select '1932-01-01 00:00'::timestamp") >>> res = cur.fetchone() >>> res [<DateTime object for '1932-01-01 00:00:00.00' at b7c58ec8>] >>> What version of Python / PostgreSQL / mxDateTime are you using? ---------------------------------------------------------------------- Comment By: Harald Armin Massa (ghum) Date: 2005-10-13 10:07 Message: Logged In: YES user_id=665785 additional information: its with the september 2005 version (interim) workaround: use to_char(datefield,'YYYY-MM-DD HH24:MI:SS') instead of datefield in your selects ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=1325835&group_id=16528 |