[BUG] Postgres interface uses db_name instead of revision_db_name

appnexus / schema-tool

framework-agnostic, schema management tool for everyone

Other

40 stars 21 forks source link

[BUG] Postgres interface uses db_name instead of revision_db_name #54

Closed qzk closed 9 years ago

qzk commented 9 years ago

db_name = database name where the alters are to be applied revision_db_name = database name where the revision history is tracked

With the bug present, revision_db_name field is ignored and history changes still get stored at db_name. Bug's effect isn't noticed if both database names are the same which is what's been the case up till now.

landscape-bot commented 9 years ago

Code quality remained the same when pulling 1fb21ad on qzk:postgres_revision_db_bug into 1e7496e on appnexus:master.