Update of /usr/cvs/Public/pygresql/docs
In directory druid.net:/tmp/cvs-serv14329/docs

Modified Files:
        changelog.txt future.txt 
Log Message:
Let execute() and executemany() methods return the cursor object. Removed an 
unnecessary call in executemany().
To see the diffs for this commit:
   
http://www.druid.net/pygresql/viewcvs.cgi/cvs/pygresql/docs/changelog.txt.diff?r1=1.39&r2=1.40

Index: changelog.txt
===================================================================
RCS file: /usr/cvs/Public/pygresql/docs/changelog.txt,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- changelog.txt       5 Dec 2008 15:00:18 -0000       1.39
+++ changelog.txt       2 Apr 2009 22:18:59 -0000       1.40
@@ -2,6 +2,12 @@
 PyGreSQL ChangeLog
 ==================
 
+Version 4.x
+-----------
+- The execute() and executemany() methods now return the cursor object,
+  so you can now write statemens like "for row in cursor.execute(...)"
+  (as suggested by Adam Frederick).
+
 Version 4.0 (2009-01-01)
 ------------------------
 - Dropped support for Python below 2.3 and PostgreSQL below 7.4.

   
http://www.druid.net/pygresql/viewcvs.cgi/cvs/pygresql/docs/future.txt.diff?r1=1.28&r2=1.29

Index: future.txt
===================================================================
RCS file: /usr/cvs/Public/pygresql/docs/future.txt,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- future.txt  5 Dec 2008 15:25:55 -0000       1.28
+++ future.txt  2 Apr 2009 22:18:59 -0000       1.29
@@ -8,9 +8,10 @@
 
 - Documentation for the pgdb module (everything specific to PyGreSQL).
 - The large object and direct access functions need much more attention.
+- The fetch method should use real cursors.
 - The C module needs to be cleaned up and redundant code merged,
   and should get its own unit test module.
-- The fetch method should use real cursors.
+- Clean up test_pg.py and merge it with TEST_PyGreSQL_classic.py.
 - What shall we do with the "tutorial" directory
   (it's rather a tutorial for Postgres/SQL than for PyGreSQL,
   it's using only the query method from the classic pg module and

_______________________________________________
PyGreSQL mailing list
[email protected]
http://mailman.vex.net/mailman/listinfo/pygresql

Reply via email to