Author: cito Date: Fri Jan 15 12:46:53 2016 New Revision: 754 Log: Fix bad reference in pgdb docs
Modified: branches/4.x/docs/contents/pgdb/cursor.rst trunk/docs/contents/pgdb/cursor.rst Modified: branches/4.x/docs/contents/pgdb/cursor.rst ============================================================================== --- branches/4.x/docs/contents/pgdb/cursor.rst Fri Jan 15 12:42:23 2016 (r753) +++ branches/4.x/docs/contents/pgdb/cursor.rst Fri Jan 15 12:46:53 2016 (r754) @@ -91,8 +91,8 @@ rows in a single operation, but this kind of usage is deprecated: :meth:`pgdbCursor.executemany` should be used instead. -Note that in case this method raises a :exception:`DatabaseError`, you can -get information about the error condition that has occurred by introspecting +Note that in case this method raises a :exc:`DatabaseError`, you can get +information about the error condition that has occurred by introspecting its :attr:`DatabaseError.sqlstate` attribute, which will be the ``SQLSTATE`` error code associated with the error. Applications that need to know which error condition has occurred should usually test the error code, rather than Modified: trunk/docs/contents/pgdb/cursor.rst ============================================================================== --- trunk/docs/contents/pgdb/cursor.rst Fri Jan 15 12:42:23 2016 (r753) +++ trunk/docs/contents/pgdb/cursor.rst Fri Jan 15 12:46:53 2016 (r754) @@ -96,8 +96,8 @@ rows in a single operation, but this kind of usage is deprecated: :meth:`Cursor.executemany` should be used instead. -Note that in case this method raises a :exception:`DatabaseError`, you can -get information about the error condition that has occurred by introspecting +Note that in case this method raises a :exc:`DatabaseError`, you can get +information about the error condition that has occurred by introspecting its :attr:`DatabaseError.sqlstate` attribute, which will be the ``SQLSTATE`` error code associated with the error. Applications that need to know which error condition has occurred should usually test the error code, rather than _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo.cgi/pygresql
