Mike Bayer b2cd9aca54 don't enable "fast insert executemany" for ON CONFLICT etc ...

Fixed issue where using the PostgreSQL "INSERT..ON CONFLICT" structure
would fail to work with the psycopg2 driver if it were used in an
"executemany" context along with bound parameters in the "SET" clause, due
to the implicit use of the psycopg2 fast execution helpers which are not
appropriate for this style of INSERT statement. Additional checks to
exclude this kind of statement from that particular extension have been
added.

Fixes: #6581
Change-Id: I3d6169e7e188dc087d1d1bfba9a42162db183265

2021-06-04 19:45:45 -04:00

..

__init__.py

refactor test suites for postgresql, mssql, mysql into packages.

2013-06-28 22:30:11 -04:00

test_async_pg_py3k.py

run handle error for commit/rollback fail and cancel transaction

2021-01-15 17:51:34 -05:00

test_compiler.py

Test some complex update cases in the pg dialect

2021-05-27 20:49:44 +02:00

test_dialect.py

Update black flak8 and zimports

2021-05-12 22:10:19 +02:00

test_on_conflict.py

don't enable "fast insert executemany" for ON CONFLICT etc

2021-06-04 19:45:45 -04:00

test_query.py

Apply quoting to render_derived() names

2021-04-01 13:41:44 -04:00

test_reflection.py

Repair PGInspector

2021-03-31 11:50:26 -04:00

test_types.py

Update black flak8 and zimports

2021-05-12 22:10:19 +02:00