From: Gerhard H?r. <gha...@us...> - 2002-10-02 11:49:14
|
Update of /cvsroot/pypgsql/pypgsql In directory usw-pr-cvs1:/tmp/cvs-serv8423 Modified Files: TODO Log Message: *p Implement an arbitrary precision type for Python by wrapping MAPM (http://www.tc.umn.edu/~ringx004/mapm-main.html). Then customize the type to behave like a PostgreSQL NUMERIC (gh) * Develop test cases for reading and writing all data types from/to PostgreSQL. * Make pyPgSQL compatible with PostgreSQL 7.3 (Beta). Make the testcases compatible with PostgreSQL 7.2 and 7.3. This requires special-casing the access to the system catalogs for the various backend versions. Index: TODO =================================================================== RCS file: /cvsroot/pypgsql/pypgsql/TODO,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** TODO 25 Sep 2002 14:17:26 -0000 1.3 --- TODO 2 Oct 2002 11:49:10 -0000 1.4 *************** *** 27,34 **** PostgreSQL data type? ! * Reimplement PgNumeric using a BSD-licensed fixed point library * Don't use floats in PgMoney. Make PgMoney a subclass of PgNumeric instead. PERFORMANCE =========== --- 27,38 ---- PostgreSQL data type? ! * Implement an arbitrary precision type for Python by wrapping MAPM ! (http://www.tc.umn.edu/~ringx004/mapm-main.html). Then customize the type to ! behave like a PostgreSQL NUMERIC (gh) * Don't use floats in PgMoney. Make PgMoney a subclass of PgNumeric instead. + * Develop test cases for reading and writing all data types from/to PostgreSQL. + PERFORMANCE =========== *************** *** 75,78 **** --- 79,86 ---- * Make PgResultSet(ConcreteClass) pickleable. This will probably involve using the copy_reg module. + + * Make pyPgSQL compatible with PostgreSQL 7.3 (Beta). Make the testcases + compatible with PostgreSQL 7.2 and 7.3. This requires special-casing the + access to the system catalogs for the various backend versions. |