Happy New Year to everybody, too. > What I would like to do is revamp the entire pg or "classical" module > to work as a subclass of pgdb, the DB-API module. The idea would be > to drop things like getresult(), dictresult(), etc. from the C code > and implement them as python methods using the pgdb module. Ideally > we can make pg.py work with any generic DB-API module, even ones not > based on PostgreSQL.
Sounds like a good idea. Since this is a greater change, maybe you should create a new branch for this. Also I wonder whether we should require more recent Postgres and Python versions (like PG 8 and Py 2.4) for the new branch so we can take advantage of new features and don't need to care for backward compatibility. E.g. it would be nice to support the "with" statement of Python 2.5 (http://www.mail-archive.com/[email protected]/msg00510.html). > As part of this work I would like to see the rows returned from > getresult, dictresult and even fetch to return a result object that > acts as a dict or list but fetches one row (or block of rows) at a > time. You mean as new methods? Because we should keep compatibility with the old API as much as possible. > Also, I would like to move the functions that convert the strings > returned into the various types into the Python side and allow the > user to overwite or add to the types. This is designed to deal with > the long outstanding TODO of handling user defined types. Agree, that would be a big progress. -- Christoph _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
