Open designermonkey opened 3 years ago
I will point out that my migrations use up
and down
methods as I have custom sql (if it's MySQL) to run that isn't possible to run in the change
method.
I had my migrations simply named as they are not date specific, so the files are not using real dates as shown above. Technically speaking they are real dates, so why would this fail?
:( I'm seeing this behavior as well with phinx 0.9.2.
I am tearing my hair out here. Given I have the following Symfony commands:
I cannot figure out why phinx refuses to see the migrations that have been applied to roll them back!
Works fine and creates the correct tables and migrations in the right table.
This command never works and always tells me there are no migrations to rollback, even though it is the exact same config and the records are present in the database.
Even if I run rollback as a
phinx
command on the cli with the right config and settings, I still get 'no migrations to rollback'.If anyone has any insight I would greatly appreciate it.