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 (cherry picked from commit f39e692d1249aeffb4de85987f6a74303fc5dcc5) Conflicts: lib/sqlalchemy/dialects/sqlite/base.py
(cherry picked from commit 4c90f355fd552e70009ffcdf3fdde9f3653e337e)
non-Integer column types, fixes #2075
(cherry picked from commit 6ac0555eaa6363ac9d0ad6566248dd294ad61d9e)
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. (cherry picked from commit 30ce7e93f4068b00ced0db785fdd578dc8a45975)
levels; :meth:`.Connection.get_isolation_level`, :attr:`.Connection.default_isolation_level`. - enhance documentation inter-linkage between new accessors, existing isolation_level parameters, as well as in the dialect-level methods which should be fully covered by Engine/Connection level APIs now. (cherry picked from commit c3d898e8d06c7e549bb273fc8654f5d24fab2204)
and extensions into an external library, and also reorganizes most large documentation pages into many small areas to reduce scrolling and better present the context into a more fine-grained hierarchy. (cherry picked from commit 9561321d0328df270c4ff0360dc7a035db627949) - manually port previous differences between 0.9 and 1.0 docs to the cherry-pick.