Update of /usr/cvs/Public/pygresql/docs
In directory druid.net:/tmp/cvs-serv22355/docs
Modified Files:
changelog.txt future.txt
Log Message:
Added support for PQescapeStringConn() and PQescapeByteaConn(). Promoted the
_quote() functions to methods of the connection. Made them use the former
functions instead of manually and faulitly handling backslashes and quotes.
To see the diffs for this commit:
http://www.druid.net/pygresql/viewcvs.cgi/cvs/pygresql/docs/changelog.txt.diff?r1=1.24&r2=1.25
Index: changelog.txt
===================================================================
RCS file: /usr/cvs/Public/pygresql/docs/changelog.txt,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- changelog.txt 19 Nov 2008 18:42:58 -0000 1.24
+++ changelog.txt 21 Nov 2008 21:17:53 -0000 1.25
@@ -19,7 +19,9 @@
- Allow DB wrapper to be used with DB-API 2 connections
(as suggested by Chris Hilton).
- Made private attributes of DB wrapper accessible.
-- Dropped dependence on mx.DateTime module
+- Dropped dependence on mx.DateTime module.
+- Support for PQescapeStringConn() and PQescapeByteaConn();
+ these are now also used by the internal _quote() functions.
Version 3.8.1 (2006-06-05)
--------------------------
http://www.druid.net/pygresql/viewcvs.cgi/cvs/pygresql/docs/future.txt.diff?r1=1.16&r2=1.17
Index: future.txt
===================================================================
RCS file: /usr/cvs/Public/pygresql/docs/future.txt,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- future.txt 21 Nov 2008 19:25:27 -0000 1.16
+++ future.txt 21 Nov 2008 21:17:53 -0000 1.17
@@ -6,13 +6,9 @@
To Do
-----
-- Use PQescapeStringConn in the _quote() function of pg and pgdb
- (escaping via backslash is not standard and produces warnings
- in newer PostgreSQL versions).
- Code marked with XXX in the pg module
- pg relies on OIDs, but these are not generated by default any more
(at least docs should recommend setting default_with_oids=true).
-- install.txt talks about MSVC 2003, we should try using 2005/2008
- 64 bit int typecasting in pgdb module
(see http://mailman.vex.net/pipermail/pygresql/2008-March/001943.html).
- Support composite primary keys
_______________________________________________
PyGreSQL mailing list
[email protected]
http://mailman.vex.net/mailman/listinfo/pygresql
