]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
projects / thirdparty / sqlalchemy / sqlalchemy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 71feeb3) | patch
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:44 +0000 (18:07 -0400)
commitcc7878dc4ae49da1444b2115cd49ebadaf17a60c
treed1efb206f22787f8d6db797f5ce8555e15d194dbtree | snapshot
parent71feeb37ca8e6726327aa1f24cf7de458dea6f82commit | diff
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
(cherry picked from commit 248d232459e38561999c4172acaaddd651c1a933)
doc/build/changelog/unreleased_14/7291.rst [new file with mode: 0644] blob
lib/sqlalchemy/engine/util.py diff | blob | blame | history
test/engine/test_execute.py diff | blob | blame | history
Mirror of https://github.com/sqlalchemy/sqlalchemy.git