Updated version 2.2.3 -> 2.3 in the docs.

This commit is contained in:
Daniele Varrazzo 2010-11-05 12:38:49 +00:00
parent ee71e52269
commit 04b4649d03
5 changed files with 8 additions and 8 deletions

View File

@ -208,7 +208,7 @@ read:
Asynchronous notifications Asynchronous notifications
-------------------------- --------------------------
.. versionchanged:: 2.2.3 .. versionchanged:: 2.3
Added `~psycopg2.extensions.Notify` object allowing to retrieve Added `~psycopg2.extensions.Notify` object allowing to retrieve
the notification payload if connected to a PostgreSQL 9.0 server. the notification payload if connected to a PostgreSQL 9.0 server.

View File

@ -106,7 +106,7 @@ The ``connection`` class
.. rubric:: Two-phase commit support methods .. rubric:: Two-phase commit support methods
.. versionadded:: 2.2.3 .. versionadded:: 2.3
.. seealso:: :ref:`tpc` for an introductory explanation of these methods. .. seealso:: :ref:`tpc` for an introductory explanation of these methods.
@ -362,7 +362,7 @@ The ``connection`` class
For other details see :ref:`async-notify`. For other details see :ref:`async-notify`.
.. versionchanged:: 2.2.3 .. versionchanged:: 2.3
Notifications are instances of the `!Notify` object. Previously the Notifications are instances of the `!Notify` object. Previously the
list was composed by 2 items tuples :samp:`({pid},{channel})` and list was composed by 2 items tuples :samp:`({pid},{channel})` and
the payload was not accessible. To keep backward compatibility, the payload was not accessible. To keep backward compatibility,

View File

@ -109,7 +109,7 @@ functionalities defined by the |DBAPI|_.
.. autoclass:: Notify(pid, channel, payload='') .. autoclass:: Notify(pid, channel, payload='')
:members: pid, channel, payload :members: pid, channel, payload
.. versionadded:: 2.2.3 .. versionadded:: 2.3
.. autoclass:: Xid(format_id, gtrid, bqual) .. autoclass:: Xid(format_id, gtrid, bqual)
@ -463,7 +463,7 @@ internal usage and Python code should not rely on them.
to the database until the transaction is finished with to the database until the transaction is finished with
`~connection.tpc_commit()` or `~connection.tpc_rollback()`. `~connection.tpc_commit()` or `~connection.tpc_rollback()`.
.. versionadded:: 2.2.3 .. versionadded:: 2.3

View File

@ -93,7 +93,7 @@ Logging cursor
Hstore data type Hstore data type
---------------- ----------------
.. versionadded:: 2.2.3 .. versionadded:: 2.3
The |hstore|_ data type is a key-value store embedded in PostgreSQL. It has The |hstore|_ data type is a key-value store embedded in PostgreSQL. It has
been available for several server versions but with the release 9.0 it has been available for several server versions but with the release 9.0 it has

View File

@ -301,7 +301,7 @@ the SQL string that would be sent to the database.
.. |hstore| replace:: :sql:`hstore` .. |hstore| replace:: :sql:`hstore`
.. _hstore: http://www.postgresql.org/docs/9.0/static/hstore.html .. _hstore: http://www.postgresql.org/docs/9.0/static/hstore.html
.. versionadded:: 2.2.3 .. versionadded:: 2.3
the :sql:`hstore` adaptation. the :sql:`hstore` adaptation.
.. index:: .. index::
@ -561,7 +561,7 @@ using the |lo_import|_ and |lo_export|_ libpq functions.
Two-Phase Commit protocol support Two-Phase Commit protocol support
--------------------------------- ---------------------------------
.. versionadded:: 2.2.3 .. versionadded:: 2.3
Psycopg exposes the two-phase commit features available since PostgreSQL 8.1 Psycopg exposes the two-phase commit features available since PostgreSQL 8.1
implementing the *two-phase commit extensions* proposed by the |DBAPI|. implementing the *two-phase commit extensions* proposed by the |DBAPI|.