Added notes about stuff changed in ver. 2.0.14.

This commit is contained in:
Daniele Varrazzo 2010-02-26 00:37:09 +00:00
parent 97ced0d4f1
commit 140e6ad4f2
2 changed files with 6 additions and 8 deletions

View File

@ -182,7 +182,7 @@ deal with Python objects adaptation:
>>> Binary("\x00\x08\x0F").getquoted() >>> Binary("\x00\x08\x0F").getquoted()
"'\\\\000\\\\010\\\\017'" "'\\\\000\\\\010\\\\017'"
.. versionchanged:: 2.0.14(ish) .. versionchanged:: 2.0.14
previously the adapter was not exposed by the `extensions` previously the adapter was not exposed by the `extensions`
module. In older version it can be imported from the implementation module. In older version it can be imported from the implementation
module `!psycopg2._psycopg`. module `!psycopg2._psycopg`.

View File

@ -286,15 +286,13 @@ the SQL string that would be sent to the database.
SQL doesn't allow an empty list in the IN operator, so your code should SQL doesn't allow an empty list in the IN operator, so your code should
guard against empty tuples. guard against empty tuples.
.. note::
The IN adapter is automatically registered when the
`~psycopg2.extensions` module is imported. This behaviour may change
in the future and the adapter will probably be always active.
.. versionadded:: 2.0.6 .. versionadded:: 2.0.6
the tuple :sql:`IN` adaptation. the tuple :sql:`IN` adaptation.
.. versionchanged:: 2.0.14
the tuple :sql:`IN` adapter is always active. In previous releases it
was necessary to import the `~psycopg2.extensions` module to have it
registered.
.. index:: .. index::
single: Unicode single: Unicode