Mike Bayer 00dae5f77e - The rendering of a :class:~sqlalchemy.schema.ForeignKeyConstraint ... will now ensure that the names of the source and target columns are the database-side name of each column, and not the value of the ``.key`` attribute as may be set only on the Python side. This is because Alembic generates the DDL for constraints as standalone objects without the need to actually refer to an in-Python :class:`~sqlalchemy.schema.Table` object, so there's no step that would resolve these Python-only key names to database column names. fixes #259		2015-01-10 17:08:03 -05:00
..
__init__.py	- fix long lines within package	2014-09-09 16:35:40 -04:00
api.py	- refactor the FK merge a bit	2014-11-30 18:02:57 -05:00
compare.py	- name the include_object hook "foreign_key_constraint"	2014-11-30 18:52:32 -05:00
render.py	- The rendering of a :class:~sqlalchemy.schema.ForeignKeyConstraint	2015-01-10 17:08:03 -05:00