PostgreSQL foreign key inspection includes options
#2183: Metadata.reflect() foreign keys include options when the dialect exposes it
ForeignKeyConstraint reflection test respects MySQL limitations
- :func:`.attributes.get_history()` when used with a scalar column-mapped
attribute will now honor the "passive" flag
passed to it; as this defaults to ``PASSIVE_OFF``, the function will
by default query the database if the value is not present.
This is a behavioral change vs. 0.8.  [ticket:2787]
- Added new method :meth:`.AttributeState.load_history`, works like
:attr:`.AttributeState.history` but also fires loader callables.
Merge branch 'master' of github.com:ijl/sqlalchemy into merge_2183
- Fix and test parsing of MySQL foreign key options within reflection;
this complements the work in :ticket:`2183` where we begin to support
reflection of foreign key options such as ON UPDATE/ON DELETE
cascade. [ticket:2839]
- move this test to PG test_reflection
- don't use locals()
- changelog for [ticket:2183]
- catch the metadata on ScalarTest.test_scalar_proxy, this has been leaving itself
around for a long time
- association proxy now returns None for proxied scalar that is also None, rather
than raising AttributeError. [ticket:2810]
python2 pickle here fails