Psycopg2

Latest version: v2.9.9

Safety actively analyzes 630217 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 12 of 14

2.0

-------------------------

* Fixed handle leak on win32.

* If available the new "safe" encoding functions of libpq are used.

* django and tinyerp people, please switch to psycopg 2 _without_
using a psycopg 1 compatibility layer (this release was anticipated
so that you all stop grumbling about psycopg 2 is still in beta.. :)

What's new in psycopg 2.0 beta 7
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* Ironed out last problems with times and date (should be quite solid now.)

* Fixed problems with some arrays.

* Slightly better ZPsycopgDA (no more double connection objects in the menu
and other minor fixes.)

* ProgrammingError exceptions now have three extra attributes: .cursor
(it is possible to access the query that caused the exception using
error.cursor.query), .pgerror and .pgcode (PostgreSQL original error
text and code.)

* The build system uses pg_config when available.

* Documentation in the doc/ directory! (With many kudos to piro.)

What's new in psycopg 2.0 beta 6
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* Support for named cursors.

* Safer parsing of time intervals.

* Better parsing of times and dates, no more locale problems.

* Should now play well with py2exe and similar tools.

* The "decimal" module is now used if available under Python 2.3.

What's new in psycopg 2.0 beta 5
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* Fixed all known bugs.

* The initial isolation level is now read from the server and
.set_isolation_level() now takes values defined in psycopg2.extensions.

* .callproc() implemented as a SELECT of the given procedure.

* Better docstrings for a few functions/methods.

* Some time-related functions like psycopg2.TimeFromTicks() now take the
local timezone into account. Also a tzinfo object (as per datetime module
specifications) can be passed to the psycopg2.Time and psycopg2.Datetime
constructors.

* All classes have been renamed to exist in the psycopg2._psycopg module,
to fix problems with automatic documentation generators like epydoc.

* NOTIFY is correctly trapped.

What's new in psycopg 2.0 beta 4
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* psycopg module is now named psycopg2.

* No more segfaults when a UNICODE query can't be converted to the
backend encoding.

* No more segfaults on empty queries.

* psycopg2.connect() now takes an integer for the port keyword parameter.

* "python setup.py bdist_rpm" now works.

* Fixed lots of small bugs, see ChangeLog for details.

What's new in psycopg 2.0 beta 3
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* ZPsycopgDA now works (except table browsing.)

* psycopg build again on Python 2.2.

What's new in psycopg 2.0 beta 2
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* Fixed ZPsycopgDA version check (ZPsycopgDA can now be imported in
Zope.)

* psycopg.extras.DictRow works even after a new query on the generating
cursor.

* Better setup.py for win32 (should build with MSCV or mingw.)

* Generic fixed and memory leaks plugs.

What's new in psycopg 2.0 beta 1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* Officially in beta (i.e., no new features will be added.)

* Array support: list objects can be passed as bound variables and are
correctly returned for array columns.

* Added the psycopg.psycopg1 compatibility module (if you want instant
psycopg 1 compatibility just "from psycopg import psycopg1 as psycopg".)

* Complete support for BYTEA columns and buffer objects.

* Added error codes to error messages.

* The AsIs adapter is now exported by default (also Decimal objects are
adapted using the AsIs adapter (when str() is called on them they
already format themselves using the right precision and scale.)

* The connect() function now takes "connection_factory" instead of
"factory" as keyword argument.

* New setup.py code to build on win32 using mingw and better error
messages on missing datetime headers,

* Internal changes that allow much better user-defined type casters.

* A lot of bugfixes (binary, datetime, 64 bit arches, GIL, .executemany())

1.99.13

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* Added missing .executemany() method.

* Optimized type cast from PostgreSQL to Python (psycopg should be even
faster than before.)

1.99.12

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* .rowcount should be ok and in sync with psycopg 1.

* Implemented the new COPY FROM/COPY TO code when connection to the
backend using libpq protocol 3 (this also removes all asprintf calls:
build on win32 works again.) A protocol 3-enabled psycopg *can*
connect to an old protocol 2 database and will detect it and use the
right code.

* getquoted() called for real by the mogrification code.

1.99.11

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* 'cursor' argument in .cursor() connection method renamed to
'cursor_factory'.

* changed 'tuple_factory' cursor attribute name to 'row_factory'.

* the .cursor attribute is gone and connections and cursors are properly
gc-managed.

* fixes to the async core.

1.99.10

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* The adapt() function now fully supports the adaptation protocol
described in PEP 246. Note that the adapters registry now is indexed
by (type, protocol) and not by type alone. Change your adapters
accordingly.

* More configuration options moved from setup.py to setup.cfg.

* Fixed two memory leaks: one in cursor deallocation and one in row
fetching (.fetchXXX() methods.)

1.99.9

^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* Added simple pooling code (psycopg.pool module).

* Added DECIMAL typecaster to convert postgresql DECIMAL and NUMERIC
types (i.e, all types with an OID of NUMERICOID.) Note that the
DECIMAL typecaster does not set scale and precision on the created
objects but uses Python defaults.

* ZPsycopgDA back in and working using the new pooling code.

* Isn't that enough? :)

Page 12 of 14

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.