diff options
author | Matt Lewellyn <guruofgentoo@gmail.com> | 2019-04-03 18:39:15 -0400 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2019-04-04 10:52:29 -0400 |
commit | 97d4d15fde7999eba29c9708b65e11d82623f686 (patch) | |
tree | a9195f899a63bfddd631452d50ea09d471162350 /lib/sqlalchemy/sql/compiler.py | |
parent | b90f9b5f367b16ddc1a2d5b06b12649c3fa9efdd (diff) | |
download | sqlalchemy-97d4d15fde7999eba29c9708b65e11d82623f686.tar.gz |
MSSQL: only compile ORDER BY if it will be rendered
Fixed issue in SQL Server dialect where if a bound parameter were present in
an ORDER BY expression that would ultimately not be rendered in the SQL
Server version of the statement, the parameters would still be part of the
execution parameters, leading to DBAPI-level errors. Pull request courtesy
Matt Lewellyn.
Fixes: #4587
Closes: #4588
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4588
Pull-request-sha: 2992a473e0f6d4fc27794cfd949ba20a81fad2ca
Change-Id: Ie709aefdb1babf810bb81526289448f8cc7a4cb1
Diffstat (limited to 'lib/sqlalchemy/sql/compiler.py')
0 files changed, 0 insertions, 0 deletions