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
Hi :)
Using Cake Migration plugin, I generate the migration and schema with cake console and tested adding a field into a table using phpmyadmin locally, which then the migration file shows the create_field changes in it.
I have no experience with CakePHP, but be careful that the slug compilation does not run on your live dynos. environment variables might be different. It could create some issues.
If you perform the same migration run locally on a test database, does it create the field you expect ?
Did some quick tests again, I was able to have the fields created when I deploy to Heroku. The problem is caused by the schema migration table which stores the migration version being not consistent to the one in my local environment.
However not on dropping fields. :/
It seems that the dropping procedures are ignored
I tried to reset all migrations and added a few iterations of create and dropping fields in the migrations, seems only the create tables and create fields ones are executed.
Hi :)
Using Cake Migration plugin, I generate the migration and schema with cake console and tested adding a field into a table using phpmyadmin locally, which then the migration file shows the create_field changes in it.
I also added the heroku compile directive
When I deploy, all things went smoothly without error, the migrations are said to be completed too.
However when I check the production database, the new field was not created. Is there any way to verify if the operation was really successful?
The text was updated successfully, but these errors were encountered: