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

Modified Files:
        future.txt 
Log Message:
Minor issues.
To see the diffs for this commit:
   
http://www.druid.net/pygresql/viewcvs.cgi/cvs/pygresql/docs/future.txt.diff?r1=1.22&r2=1.23

Index: future.txt
===================================================================
RCS file: /usr/cvs/Public/pygresql/docs/future.txt,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- future.txt  23 Nov 2008 14:07:35 -0000      1.22
+++ future.txt  23 Nov 2008 14:32:18 -0000      1.23
@@ -7,10 +7,11 @@
 -----
 
 - Code marked with XXX in the pg module
-- pg relies on OIDs, but these are not generated by default any more
+- Classic pg relies on OIDs, but these are not generated by default any more
   (at least docs should recommend setting default_with_oids=true).
-- Support composite primary keys
-  (see http://mailman.vex.net/pipermail/pygresql/2006-May/001688.html).
+- Support composite primary keys and generally reconsider the pkey() method,
+  (see http://mailman.vex.net/pipermail/pygresql/2006-May/001688.html,
+  http://mailman.vex.net/pipermail/pygresql/2004-February/001282.html).
 - Documentation for the pgdb module (everything specific to PyGreSQL).
 - The large object and direct access functions need much more attention.
 - The C module needs to be cleaned up and redundant code merged,
@@ -18,17 +19,17 @@
 - The fetch method should use real cursors.
 - What shall we do with the "tutorial" directory
   (it's rather a tutorial for Postgres/SQL than for PyGreSQL,
-  it' using only the query method from the classic pg module and
+  it's using only the query method from the classic pg module and
   no other PyGreSQL functionality, it's rather a demo than a tutorial)?
 
-
 Proposed Patches
 ----------------
 
 - Notice handling with PQsetNoticeReceiver and PQsetNoticeProcessor
   (one possible implementation was already suggested by Dmitry Dvoinikov
-  http://mailman.vex.net/pipermail/pygresql/2005-November/001530.html)
-
+  http://mailman.vex.net/pipermail/pygresql/2005-November/001530.html).
+  Maybe also make notifications accessible via the optional cursor and
+  connection attribute "messages" proposed in the DB-API specs.
 
 Wish List
 ---------
@@ -37,7 +38,8 @@
 - Make use of PQexecParams() and PQprepare(). This could speed up
   executemany() and allow retrieving binary data directly by setting
   the resultFormat parameter to one.
-- Support .errorhandler extension.
+- Support optional "errorhandler" extension.
+- Support optional cursor and connection attribute "messages".
 - Connection as context manager (see http://tinyurl.com/6j9cef).
 - Users should be able to register their own types with _pg.
 - New methods in the classic module, similar to getresult() and

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

Reply via email to