(cherry picked from commit 859379e2fcc4506d036700ba1eca4c0ae526a8ee)

that have problems with right-nested joins and UNION column keys;
references #3633 references #3634.   backport from 1.1 to 0.9
announcing 1.1 as where these behaviors will be retired based
on version-specific checks
- fix test_resultset so that it passes when SQLite 3.10.0 is
present, references #3633

(cherry picked from commit 89fa08792e98b9e31452aa3c949d9b909b10e7cd)

that included non-alphabetic characters in the names, like dots or
spaces, would not be reflected with their name.
fixes #3495

non-Integer column types, fixes #2075

That is, after exhausing all rows using the fetch methods, the
DBAPI cursor is released as before and the object may be safely
discarded, but the fetch methods may continue to be called for which
they will return an end-of-result object (None for fetchone, empty list
for fetchmany and fetchall).   Only if :meth:`.ResultProxy.close`
is called explicitly will these methods raise the "result is closed"
error.
fixes #3330 fixes #3329

From https://www.sqlite.org/partialindex.html
> Partial indexes have been supported in SQLite since version 3.8.0.

Reflection does not expose the predicate of partial indexes.  The
postgresql dialect does detect such indexes and issue a warning.  I
looked into matching this level of support, but the sqlite pragma
index_info does not expose the predicate.  Getting this data would
probably require parsing the CREATE INDEX statement from sqlite_master.