diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2022-01-03 17:28:52 -0500 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2022-01-03 17:39:33 -0500 |
| commit | 709239f4a61e88c2051dce87eb4058efd653697e (patch) | |
| tree | 5c9c3c15c7e13e422a2c61fca2ccd51ca6ee94b5 /lib/sqlalchemy/dialects/mysql/base.py | |
| parent | 400bf1716f84821d63daaf0a988d725dfd55d6a0 (diff) | |
| download | sqlalchemy-709239f4a61e88c2051dce87eb4058efd653697e.tar.gz | |
ensure correlate_except is checked for empty tuple
Fixed issue where :meth:`_sql.Select.correlate_except` method, when passed
either the ``None`` value or no arguments, would not correlate any elements
when used in an ORM context (that is, passing ORM entities as FROM
clauses), rather than causing all FROM elements to be considered as
"correlated" in the same way which occurs when using Core-only constructs.
Fixes: #7514
Change-Id: Ic4a5252c8f3c1140aba6c308264948f3a91f33f5
Diffstat (limited to 'lib/sqlalchemy/dialects/mysql/base.py')
0 files changed, 0 insertions, 0 deletions