Zope.sqlalchemy

Latest version: v3.1

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

Scan your dependencies

Page 3 of 5

0.7.6

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

* Make version check in register compatible with prereleases.

0.7.5

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

* Ensure mapped objects are expired following a ``transaction.commit()`` when
no database commit was required.
(`8 <https://github.com/zopefoundation/zope.sqlalchemy/issues/8>`_)

0.7.4

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

* Allow ``session.commit()`` on nested transactions to facilitate integration
of existing code that might not use ``transaction.savepoint()``.
(`1 <https://github.com/zopefoundation/zope.sqlalchemy/issues/1>`_)

* Add a new function zope.sqlalchemy.register(), which replaces the
direct use of ZopeTransactionExtension to make use
of the newer SQLAlchemy event system to establish instrumentation on
the given Session instance/class/factory. Requires at least
SQLAlchemy 0.7.
(`4 <https://github.com/zopefoundation/zope.sqlalchemy/issues/4>`_)

* Fix `keep_session=True` doesn't work when a transaction is joined by flush
and other manngers bug.
(`5 <https://github.com/zopefoundation/zope.sqlalchemy/issues/5>`_)

0.7.3

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

* Prevent the ``Session`` object from getting into a "wedged" state if joining
a transaction fails. With thread scoped sessions that are reused this can cause
persistent errors requiring a server restart.
(`2 <https://github.com/zopefoundation/zope.sqlalchemy/issues/2>`_)

0.7.2

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

* Make life-time of sessions configurable. Specify `keep_session=True` when
setting up the SA extension.

* Python 3.3 compatibility.

0.7.1

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

* Use ``implementer`` as a class decorator instead of ``implements()`` at
class scope for compatibility with ``zope.interface`` 4.0. This requires
``zope.interface`` >= 3.6.0.

Page 3 of 5

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.