Mike Bayer ada1927529 The `deferrable keyword argument on :class:.ForeignKey` and ...

:class:`.ForeignKeyConstraint` will not render the ``DEFERRABLE`` keyword
on the MySQL dialect.  For a long time we left this in place because
a non-deferrable foreign key would act very differently than a deferrable
one, but some environments just disable FKs on MySQL, so we'll be less
opinionated here. [ticket:2721]

2013-06-03 18:33:20 -04:00

..

aaa_profiling

- zoomark tests

2013-05-26 19:47:13 -04:00

base

merge default

2013-05-23 13:02:33 -04:00

dialect

The `deferrable keyword argument on :class:.ForeignKey` and

2013-06-03 18:33:20 -04:00

engine

- clean up some of the requires for cross-schema reflection

2013-06-03 18:11:32 -04:00

ext

Fixed bug where :class:.MutableDict didn't report a change event

2013-06-03 18:23:23 -04:00

orm

Merge branch 'master' into ticket_1068

2013-06-03 13:13:16 -04:00

perf

no need for all these scripts, not worth maintaining

2013-04-28 15:02:44 -04:00

sql

Fixed bug whereby joining a select() of a table "A" with multiple

2013-06-03 17:03:15 -04:00

__init__.py

- the NoseSQLAlchemyPlugin has been moved to a

2010-10-17 15:23:14 -04:00

binary_data_one.dat

…

binary_data_two.dat

…

profiles.txt

- clean up some of the requires for cross-schema reflection

2013-06-03 18:11:32 -04:00

requirements.py

- clean up some of the requires for cross-schema reflection

2013-06-03 18:11:32 -04:00