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

Modified Files:
        future.txt pg.txt 
Log Message:
Support for PQescapeStringConn and PQescapeByteaConn.
To see the diffs for this commit:
   
http://www.druid.net/pygresql/viewcvs.cgi/cvs/pygresql/docs/future.txt.diff?r1=1.15&r2=1.16

Index: future.txt
===================================================================
RCS file: /usr/cvs/Public/pygresql/docs/future.txt,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- future.txt  21 Nov 2008 17:08:17 -0000      1.15
+++ future.txt  21 Nov 2008 19:25:27 -0000      1.16
@@ -6,8 +6,6 @@
 To Do
 -----
 
-- Support PQescapeStringConn and PQescapeByteaConn
-  (see also http://www.postgresql.org/docs/techdocs.49).
 - Use PQescapeStringConn in the _quote() function of pg and pgdb
   (escaping via backslash is not standard and produces warnings
   in newer PostgreSQL versions).

   
http://www.druid.net/pygresql/viewcvs.cgi/cvs/pygresql/docs/pg.txt.diff?r1=1.13&r2=1.14

Index: pg.txt
===================================================================
RCS file: /usr/cvs/Public/pygresql/docs/pg.txt,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- pg.txt      9 Oct 2008 21:02:16 -0000       1.13
+++ pg.txt      21 Nov 2008 19:25:27 -0000      1.14
@@ -303,6 +303,8 @@
   in SQL commands. Certain characters (such as quotes and backslashes)
   must be escaped to prevent them from being interpreted specially
   by the SQL parser. `escape_string` performs this operation.
+  Note that there is also a `pgobject` method with the same name
+  which takes connection properties into account.
 
 .. caution:: It is especially important to do proper escaping when
   handling strings that were received from an untrustworthy source.
@@ -334,6 +336,8 @@
   Escapes binary data for use within an SQL command with the type `bytea`.
   As with `escape_string`, this is only used when inserting data directly
   into an SQL command string.
+  Note that there is also a `pgobject` method with the same name
+  which takes connection properties into account.
 
 Example::
 
@@ -965,7 +969,9 @@
   :str: the escaped string
 
 Description:
-  See the module function with the same name.
+  Similar to the module function with the same name, but the
+  behavior of this method is adjusted depending on the connection properties
+  (such as character encoding).
 
 escape_bytea - escape binary data for use within SQL as type `bytea`
 --------------------------------------------------------------------
@@ -980,7 +986,9 @@
   :str: the escaped string
 
 Description:
-  See the module function with the same name.
+  Similar to the module function with the same name, but the
+  behavior of this method is adjusted depending on the connection properties
+  (in particular, whether standard-conforming strings are enabled).
 
 unescape_bytea -- unescape `bytea` data that has been retrieved as text
 -----------------------------------------------------------------------

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

Reply via email to