diff options
author | Mike Bayer <mike_mp@zzzcomputing.com> | 2017-08-31 13:12:50 -0400 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2017-08-31 13:20:57 -0400 |
commit | b9b1e374bfbcece8259a4df5372ca68d45aaaf01 (patch) | |
tree | 6bc5294257c158ffdf4409dde52ff5449c70a79b /lib/sqlalchemy/testing/provision.py | |
parent | d0470e296ea589620c94d8f2dd37e94b8f03842a (diff) | |
download | sqlalchemy-b9b1e374bfbcece8259a4df5372ca68d45aaaf01.tar.gz |
Add new sane_rowcount_w_returning flag
Added a new class of "rowcount support" for dialects that is specific to
when "RETURNING", which on SQL Server looks like "OUTPUT inserted", is in
use, as the PyODBC backend isn't able to give us rowcount on an UPDATE or
DELETE statement when OUTPUT is in effect. This primarily affects the ORM
when a flush is updating a row that contains server-calcluated values,
raising an error if the backend does not return the expected row count.
PyODBC now states that it supports rowcount except if OUTPUT.inserted is
present, which is taken into account by the ORM during a flush as to
whether it will look for a rowcount.
ORM tests are implicit in existing tests run against PyODBC
Fixes: #4062
Change-Id: Iff17cbe4c7a5742971ed85a4d58660c18cc569c2
Diffstat (limited to 'lib/sqlalchemy/testing/provision.py')
0 files changed, 0 insertions, 0 deletions