be always be correctly propagated when one CTE referred to another
aliased CTE in a statement.
Fixes #3154

sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing

as a scalar subquery such as within an IN would receive inappropriate
substitutions from the enclosing query, if the same table were present
inside the subquery as were in the enclosing query such as in a
joined inheritance scenario.
fixes #3130

to again have the chance to veto rendering, as the naming convention
can make the decision that the name is "none" or not now.

constraint convention that includes ``constraint_name`` would
then force all :class:`.Boolean` and :class:`.Enum` types to
require names as well, as these implicitly create a
constraint, even if the ultimate target backend were one that does
not require generation of the constraint such as Postgresql.
The mechanics of naming conventions for these particular
constraints has been reorganized such that the naming
determination is done at DDL compile time, rather than at
constraint/table construction time.
fixes #3067

parameters could be expressed in the wrong final order
when CTEs were nested in certain ways.
fixes #3090

to check subsequent values entries beyond the first one given
for literal SQL expressions.
fixes #3069

to get all flake8 passing

the compiled cache is used.  That allows us to cache the whole metadata
and save on creating it at result time, when compiled cache is used.

Moved initialization into else block
Conflicts:
	lib/sqlalchemy/sql/compiler.py