Mike Bayer 2ce8a04e72 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

2019-07-29 14:52:40 -04:00

..

aaa_profiling

Fix typos

2019-07-21 10:51:29 +10:00

base

Allow duplicate columns in from clauses and selectables

2019-07-11 14:20:10 -04:00

dialect

Fix typos

2019-07-21 10:51:29 +10:00

engine

Allow duplicate columns in from clauses and selectables

2019-07-11 14:20:10 -04:00

ext

Enable F841

2019-06-20 13:50:41 -04:00

orm

Don't assume m2o key is present in the dictionary

2019-07-23 09:24:32 -04:00

perf

Enable F841

2019-06-20 13:50:41 -04:00

sql

Invoke column_expression() for subsequent SELECTs in CompoundSelect

2019-07-29 14:52:40 -04:00

__init__.py

…

binary_data_one.dat

…

binary_data_two.dat

…

conftest.py

Post black reformatting

2019-01-06 18:23:11 -05:00

profiles.txt

Allow duplicate columns in from clauses and selectables

2019-07-11 14:20:10 -04:00

requirements.py

Support tuple IN VALUES for SQLite, others

2019-07-19 13:08:06 -04:00