(cherry picked from commit edc0b8678bc06ae27fa0f7e80c3eb074978fbe10)

(cherry picked from commit 859379e2fcc4506d036700ba1eca4c0ae526a8ee)

(cherry picked from commit 24dba714cb56e1f5a4dca5453cc5f442e6ee08ab)

symbols with names quoted to force all-lower-case would not be
identified properly in reflection queries.  The :class:`.quoted_name`
construct is now applied to incoming symbol names that detect as
forced into all-lower-case within the "name normalize" process.
fixes #3548

(cherry picked from commit 4578ab54a5b849fdb94a7032987f105b7ec117a4)

up SQLAlchemy's version detection under Python 3 and inadvertently
not using the correct unicode mode for Python 3.  This would cause
issues such as bound variables mis-interpreted as NULL and rows
silently not being returned.
fixes #3491

(cherry picked from commit d8efa2257ec650b345ec6e840984387263a957a6)

these files are present.

- replace force_result_map with a mini-API for nested result sets, add
coverage

The "wrapping" employed by the mssql and oracle dialects using the
"iswrapper" argument was not being used intelligently by the compiler,
and the result map was being written incorrectly, using
*more* columns in the result map than were actually returned by
the statement, due to "row number" columns that are inside the
subquery.   The compiler now writes out result map on the
"top level" select in all cases
fully, and for the mssql/oracle wrapping case extracts out
the "proxied" columns in a second step, which only includes
those columns that are proxied outwards to the top level.

This change might have implications for 3rd party dialects that
might be imitating oracle's approach.   They can safely continue
to use the "iswrapper" kw which is now ignored, but they may
need to also add the _select_wraps argument as well.