Mike Bayer c3850e57c4 downgrade batches for bindparam() in SET ...

Fixed issue where :meth:`_postgresql.Insert.on_conflict_do_update`
using parametrized bound parameters in the ``set_`` clause would fail
when used with executemany batching. For dialects that use the
``use_insertmanyvalues_wo_returning`` optimization (psycopg2),
insertmanyvalues is now disabled when there is an ON CONFLICT clause.
For cases with RETURNING, row-at-a-time mode is used when the SET
clause contains parametrized bindparams (bindparams that receive
values from the parameters dict), ensuring each row's parameters are
correctly applied. ON CONFLICT statements using expressions like
``excluded.<column>`` continue to batch normally.

Fixed issue where :meth:`_sqlite.Insert.on_conflict_do_update`
using parametrized bound parameters in the ``set_`` clause would fail
when used with executemany batching. Row-at-a-time mode is now used
for ON CONFLICT statements with RETURNING that contain parametrized
bindparams, ensuring each row's parameters are correctly applied. ON
CONFLICT statements using expressions like ``excluded.<column>``
continue to batch normally.

Fixes: #13130
Change-Id: I0c5a9142401c745d38e58d071c16e53610f9bfea

2026-02-17 16:10:42 -05:00

..

__init__.py

…

test_compiler.py

PostgreSQL / SQLite / Insert.on_conflict_do_update: respect compile_kwargs

2026-02-08 15:08:10 -05:00

test_dialect.py

…

test_on_conflict.py

downgrade batches for bindparam() in SET

2026-02-17 16:10:42 -05:00

test_reflection.py

improve sqlite reflection regex for unusual names/formats

2025-10-24 09:54:44 -04:00

test_types.py

…