]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Check for Mapping explicitly in 2.0 params
authorMike Bayer <mike_mp@zzzcomputing.com>
Thu, 4 Nov 2021 21:02:24 +0000 (17:02 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Thu, 4 Nov 2021 22:07:21 +0000 (18:07 -0400)
commit248d232459e38561999c4172acaaddd651c1a933
tree2cf38b16770ffd9e390cead0b39e9d87ae523e8d
parentfee0855bfe2982927ab21ce7398fa48b90af7ca4
Check for Mapping explicitly in 2.0 params

Fixed issue in future :class:`_future.Connection` object where the
:meth:`_future.Connection.execute` method would not accept a non-dict
mapping object, such as SQLAlchemy's own :class:`.RowMapping` or other
``abc.collections.Mapping`` object as a parameter dictionary.

Fixes: #7291
Change-Id: I819f079d86d19d1d81c570e0680f987e51e34b84
doc/build/changelog/unreleased_14/7291.rst [new file with mode: 0644]
lib/sqlalchemy/engine/util.py
test/engine/test_execute.py