Update of /usr/cvs/Public/pygresql/docs
In directory druid.net:/tmp/cvs-serv25114/docs
Modified Files:
changelog.txt pg.txt
Log Message:
Reimplemented "protocol_version" and "server_version" as attributes instead of
methods.
To see the diffs for this commit:
http://www.druid.net/pygresql/viewcvs.cgi/cvs/pygresql/docs/changelog.txt.diff?r1=1.35&r2=1.36
Index: changelog.txt
===================================================================
RCS file: /usr/cvs/Public/pygresql/docs/changelog.txt,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- changelog.txt 2 Dec 2008 22:39:56 -0000 1.35
+++ changelog.txt 3 Dec 2008 00:17:14 -0000 1.36
@@ -34,7 +34,8 @@
submitting an empty command.
- Removed compatibility code for old OID munging style.
- Added "return_changes" flag to insert method.
-- Added protocol_version() and server_version() methods.
+- Added "protocol_version" and "server_version" attributes.
+- Revived the "user" attribute.
Version 3.8.1 (2006-06-05)
--------------------------
http://www.druid.net/pygresql/viewcvs.cgi/cvs/pygresql/docs/pg.txt.diff?r1=1.20&r2=1.21
Index: pg.txt
===================================================================
RCS file: /usr/cvs/Public/pygresql/docs/pg.txt,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- pg.txt 2 Dec 2008 22:39:56 -0000 1.20
+++ pg.txt 3 Dec 2008 00:17:14 -0000 1.21
@@ -522,45 +522,6 @@
This method returns the underlying socket id used to connect
to the database. This is useful for use in select calls, etc.
-protocol_version - interrogates the frontend/backend protocol being used
-------------------------------------------------------------------------
-Syntax::
-
- protocol_version()
-
-Parameters:
- None
-
-Exceptions raised:
- :TypeError: too many (any) arguments
-
-Description:
- Applications might wish to use this to determine whether certain
- features are supported. Currently, the possible values are 2
- (2.0 protocol), 3 (3.0 protocol), or zero (connection bad).
- This will not change after connection startup is complete,
- but it could theoretically change during a connection reset.
-
-server_version - interrogates the frontend/backend protocol being used
-----------------------------------------------------------------------
-Syntax::
-
- server_version()
-
-Parameters:
- None
-
-Exceptions raised:
- :TypeError: too many (any) arguments
-
-Description:
- Applications might use this to determine the version of the database
- server they are connected to. The number is formed by converting
- the major, minor, and revision numbers into two-decimal-digit numbers
- and appending them together. For example, version 8.1.5 will be returned
- as 80105, and version 8.2 will be returned as 80200 (leading zeroes are
- not shown). Zero is returned if the connection is bad.
-
getnotify - gets the last notify from the server
------------------------------------------------
Syntax::
@@ -740,14 +701,16 @@
Every `pgobject` defines a set of read-only attributes that describe the
connection and its status. These attributes are:
- :host: the host name of the server (string)
- :port: the port of the server (integer)
- :db: the selected database (string)
- :options: the connection options (string)
- :tty: the connection debug terminal (string)
- :user: user name on the database system (string)
- :status: the status of the connection (integer: 1 - OK, 0 - bad)
- :error: the last warning/error message from the server (string)
+ :host: the host name of the server (string)
+ :port: the port of the server (integer)
+ :db: the selected database (string)
+ :options: the connection options (string)
+ :tty: the connection debug terminal (string)
+ :user: user name on the database system (string)
+ :protocol_version: the frontend/backend protocol being used (integer)
+ :server_version: the backend version (integer, e.g. 80305 for 8.3.5)
+ :status: the status of the connection (integer: 1 - OK, 0 - bad)
+ :error: the last warning/error message from the server (string)
The DB wrapper class
_______________________________________________
PyGreSQL mailing list
[email protected]
http://mailman.vex.net/mailman/listinfo/pygresql
