diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2019-07-29 14:49:22 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2019-07-29 14:52:40 -0400 |
| commit | 2ce8a04e726daecbf060684dcee7559634506700 (patch) | |
| tree | a226c22b20772a9f1cdfa4b662e9f9ea742ab9fd /lib/sqlalchemy/sql/schema.py | |
| parent | aef6e625ba5799bf5935ba3acbb62a37c9e577ca (diff) | |
| download | sqlalchemy-2ce8a04e726daecbf060684dcee7559634506700.tar.gz | |
Invoke column_expression() for subsequent SELECTs in CompoundSelect
Fixed bug where :meth:`.TypeEngine.column_expression` method would not be
applied to subsequent SELECT statements inside of a UNION or other
:class:`.CompoundSelect`, even though the SELECT statements are rendered at
the topmost level of the statement. New logic now differentiates between
rendering the column expression, which is needed for all SELECTs in the
list, vs. gathering the returned data type for the result row, which is
needed only for the first SELECT.
Fixes: #4787
Change-Id: Iceb63e430e76d2365649aa25ead09c4e2a062e10
Diffstat (limited to 'lib/sqlalchemy/sql/schema.py')
0 files changed, 0 insertions, 0 deletions