From: Andrew M. <an...@ob...> - 2005-05-23 05:55:11
|
>The issue has been fixed in CVS HEAD code base. That fixed my problem, but I think you also need to handle PG_TIMETZ. This sort of thing should have been caught by the unittests... which, btw, appear to be broken with Python 2.4: 1$ (cd test && python2.3 PgSQLTestCases.py) .................................................................. ---------------------------------------------------------------------- Ran 66 tests in 2.019s OK 1$ (cd test && python2.4 PgSQLTestCases.py) ...............F.................................................. ====================================================================== FAIL: CheckPgInt2 (__main__.PgSQLTestModuleInterface) ---------------------------------------------------------------------- Traceback (most recent call last): File "PgSQLTestCases.py", line 219, in CheckPgInt2 self.failUnless(a == 181.0, 'PgInt2 comparison to Float failed.') AssertionError: PgInt2 comparison to Float failed. ---------------------------------------------------------------------- Ran 66 tests in 0.958s FAILED (failures=1) -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ |