]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Set IDENTITY_INSERT for insert.values({column: expr})
authorMike Bayer <mike_mp@zzzcomputing.com>
Wed, 13 Feb 2019 16:26:54 +0000 (11:26 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Wed, 13 Feb 2019 16:28:10 +0000 (11:28 -0500)
commit4a24277f0dd1c07c8ec194a3ad19fe6f9d998445
tree69eea57a253cf50c42e49159c715080889c4df84
parentdb589a98b2213ec1423c98c9c152d2ba2f7efe83
Set IDENTITY_INSERT for insert.values({column: expr})

Fixed bug where the SQL Server "IDENTITY_INSERT" logic that allows an INSERT
to proceed with an explicit value on an IDENTITY column was not detecting
the case where :meth:`.Insert.values` were used with a dictionary that
contained a :class:`.Column` as key and a SQL expression as a value.

Fixes: #4499
Change-Id: Ia61cd6524b030b40a665db9c20771f0c5aa5fcd7
(cherry picked from commit 71d642711d26ee8e1e7e8b19d70be8be1eca22eb)
doc/build/changelog/unreleased_12/4499.rst [new file with mode: 0644]
lib/sqlalchemy/dialects/mssql/base.py
test/dialect/mssql/test_query.py
test/orm/test_unitofwork.py