diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2023-04-05 12:59:13 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2023-04-05 18:24:59 -0400 |
| commit | 7fb7365622ee751b264bbbd4e7394ef8e81d45c5 (patch) | |
| tree | 4d094f22847406e47cf2191b96c8057ec8ee5418 /lib/sqlalchemy/dialects/postgresql/base.py | |
| parent | e79ab08165e01dc7af50fcffadb31468ace51b6c (diff) | |
| download | sqlalchemy-7fb7365622ee751b264bbbd4e7394ef8e81d45c5.tar.gz | |
turn off use_insertmanyvalues for SQL Server
we will keep trying to find workarounds, however this
patch is the "turn it off" patch
Due to a critical bug identified in SQL Server, the SQLAlchemy
"insertmanyvalues" feature which allows fast INSERT of many rows while also
supporting RETURNING unfortunately needs to be disabled for SQL Server. SQL
Server is apparently unable to guarantee that the order of rows inserted
matches the order in which they are sent back by OUTPUT inserted when
table-valued rows are used with INSERT in conjunction with OUTPUT inserted.
We are trying to see if Microsoft is able to confirm this undocumented
behavior however there is no known workaround, other than it's not safe to
use table-valued expressions with OUTPUT inserted for now.
Fixes: #9603
Change-Id: I4b932fb8774390bbdf4e870a1f6cfe9a78c4b105
Diffstat (limited to 'lib/sqlalchemy/dialects/postgresql/base.py')
0 files changed, 0 insertions, 0 deletions