Author: cito Date: Tue Nov 6 15:30:58 2012 New Revision: 465 Log: Updated the changelog and future documents.
Modified: trunk/docs/changelog.txt trunk/docs/future.txt Modified: trunk/docs/changelog.txt ============================================================================== --- trunk/docs/changelog.txt Tue Nov 6 14:37:49 2012 (r464) +++ trunk/docs/changelog.txt Tue Nov 6 15:30:58 2012 (r465) @@ -13,6 +13,10 @@ - The classic API now supports a method namedresult() in addition to getresult() and dictresult(), which returns the rows of the result as named tuples if these are supported (Python 2.6 or higher). +- The classic API has got the new methods begin(), commit(), rollback(), + savepoint() and release() for handling transactions. +- Both classic and DBAPI 2 connections can now be used as context + managers for encapsulating transactions. - The execute() and executemany() methods now return the cursor object, so you can now write statements like "for row in cursor.execute(...)" (as suggested by Adam Frederick). @@ -25,7 +29,7 @@ - The getnotify() method can now also return payload strings (#15). - Better support for notice processing with the new methods set_notice_receiver() and get_notice_receiver() - (as suggested by Michael Filonenko, see #37). + (as suggested by Michael Filonenko, see #12 and #37). - Open transactions are rolled back when pgdb connections are closed (as suggested by Peter Harris, see #46). - Connections and cursors can now be used with the "with" statement Modified: trunk/docs/future.txt ============================================================================== --- trunk/docs/future.txt Tue Nov 6 14:37:49 2012 (r464) +++ trunk/docs/future.txt Tue Nov 6 15:30:58 2012 (r465) @@ -23,20 +23,9 @@ the classic pg module and no other PyGreSQL functionality, it's rather a demo than a tutorial (#11)? -Proposed Patches ----------------- - -- Notice handling with PQsetNoticeReceiver and PQsetNoticeProcessor - (one possible implementation was already suggested by Dmitry Dvoinikov - https://mail.vex.net/mailman/private.cgi/pygresql/2005-November/001530.html). - Maybe also make notifications accessible via the optional cursor and - connection attribute "messages" proposed in the DB-API specs (#12). - Wish List --------- -- Make SQLSTATE error codes available (#13). -- Support the new listen/notify infrastructure of PostgreSQL 9.0 (#15). - Make use of PQexecParams() and PQprepare(). This could speed up executemany() and allow retrieving binary data directly by setting the resultFormat parameter to one (#16). @@ -44,11 +33,10 @@ available with PQfmod() or PQftable() for instance (#17). - Support optional "errorhandler" extension (#18). - Support optional cursor and connection attribute "messages" (#19). -- Connection as context manager (see http://tinyurl.com/32bx6xo) (#20). - Users should be able to register their own types with _pg (#21). -- Let pg and pgdb support namedtuples (as available in Py 2.6). - pg could get a new method namedresult(), and pgdb could provide - a row factory for namedtuples (similar to sqlite3) (#22). +- pg has now got a new method namedresult() that returns named tuples. + pgdb should also support named tuples, maybe via a row_factory attribute + on the connection, similar to sqlite3 (see #22). - New methods in the classic module, similar to getresult() and dictresult(), but returning dictionaries of rows instead of lists of rows (with primary key or oids as keys) (#23). _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo.cgi/pygresql
