You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I create next migration with some changes. (it has now matter which. Just add some field to any table for example). While doing that I get the warning:
Overwriting existing upgrade-diff file - /home/kes/work/projects/tucha/monkeyman/share/migrations/PostgreSQL/upgrade/129-130/001-auto.sql at /home/kes/work/projects/tucha/monkeyman/local/lib/perl5/DBIx/Class/DeploymentHandler/WithReasonableDefaults.pm line 18.
SQL::Translator::Diff::schema_diff(): Renamed column can't find old column "order.last_bill_date" for renamed column
The warning come when deploy/129/001-auto.yml file is accessed/analized
I do not understand why it says that last_bill_date can not be found. It is obvious why: for scheme 129 the column last_bill_date was renamed to billed_to.
last_bill_date was at 128 scheme and there is no such field at 129 scheme. DBIx::Class::Migration should not try to find last_bill_date for 129, to my mind
How to reproduce.
Change the definition of your column
produced SQL's for upgrade and downgrade:
Upgrade:
Downgrade:
The text was updated successfully, but these errors were encountered: