diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2018-07-14 12:26:29 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2018-07-14 13:11:53 -0400 |
| commit | fb377229cd4c4e503bde9c44b78d30ad48f3cf7e (patch) | |
| tree | 028747fa14cfc3eefc4003744e371c5e809626f8 /lib/sqlalchemy/dialects/sqlite | |
| parent | a5d4653b6e26420a61be6e80fef8a0645cb64ceb (diff) | |
| download | sqlalchemy-fb377229cd4c4e503bde9c44b78d30ad48f3cf7e.tar.gz | |
Don't apply no-traverse to query.statement
Fixed long-standing issue in :class:`.Query` where a scalar subquery such
as produced by :meth:`.Query.exists`, :meth:`.Query.as_scalar` and other
derivations from :attr:`.Query.statement` would not correctly be adapted
when used in a new :class:`.Query` that required entity adaptation, such as
when the query were turned into a union, or a from_self(), etc. The change
removes the "no adaptation" annotation from the :func:`.select` object
produced by the :attr:`.Query.statement` accessor.
Change-Id: I554e0e909ac6ee785ec3b3b14aaec9d235aa28cf
Fixes: #4304
Diffstat (limited to 'lib/sqlalchemy/dialects/sqlite')
0 files changed, 0 insertions, 0 deletions
