0.7.4

0.7.4

Released: January 12, 2015

• [autogenerate] [bug] [postgresql] Repaired issue where a server default specified without text()
  that represented a numeric or floating point (e.g. with decimal places)
  value would fail in the Postgresql-specific check for "compare server
  default"; as PG accepts the value with quotes in the table specification,
  it's still valid. Pull request courtesy Dimitris Theodorou.

  References: #241

• [autogenerate] [bug] The rendering of a ~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
  ~sqlalchemy.schema.Table object, so there's no step that
  would resolve these Python-only key names to database column names.

  References: #259

• [autogenerate] [bug] Fixed bug in foreign key autogenerate where if the in-Python table
  used custom column keys (e.g. using the key='foo' kwarg to
  Column), the comparison of existing foreign keys to those specified
  in the metadata would fail, as the reflected table would not have
  these keys available which to match up. Foreign key comparison for
  autogenerate now ensures it's looking at the database-side names
  of the columns in all cases; this matches the same functionality
  within unique constraints and indexes.

  References: #260

• [autogenerate] [bug] Fixed issue in autogenerate type rendering where types that belong
  to modules that have the name "sqlalchemy" in them would be mistaken
  as being part of the sqlalchemy. namespace. Pull req courtesy
  Bartosz Burclaf.

  References: #261