]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
send same sub_stmt to after_cursor_execute as before
authorMike Bayer <mike_mp@zzzcomputing.com>
Wed, 3 Dec 2025 04:10:10 +0000 (23:10 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Wed, 3 Dec 2025 04:10:10 +0000 (23:10 -0500)
commit6924f6c5d91be83dd646c3290d53c98afeca4d37
treed4570daedb62db99dc1504a6c35b347f4ffbc6fd
parentc5d09f5ed4b4e37cfdd033026e2f67382ee9fcb3
send same sub_stmt to after_cursor_execute as before

Fixed issue in the :meth:`.ConnectionEvents.after_cursor_execute` method
where the SQL statement and parameter list for an "insertmanyvalues"
operation sent to the event would not be the actual SQL / parameters just
emitted on the cursor, instead being the non-batched form of the statement
that's used as a template to generate the batched statements.

Fixes: #13018
Change-Id: Ib5b6c576f2c7a9ed275de30290d619cc651b4816
doc/build/changelog/unreleased_21/13018.rst [new file with mode: 0644]
lib/sqlalchemy/engine/base.py
lib/sqlalchemy/testing/assertsql.py
test/engine/test_execute.py