Closed gabrielhpugliese closed 4 years ago
your migrations are wrong (there is no such option as primary, only primaryKey) not db-migrate, please read the documentation more carefully before opening an issue like this and make sure you're not doing it wrong:
https://db-migrate.readthedocs.io/en/latest/API/SQL/#createtabletablename-columnspec-callback
Sorry about it. Thanks.
Current behavior
Old migrations and new ones do not output auto increment anymore to any column
Expected behavior
SQL output should add auto increment to column
Minimal reproduction of the problem with instructions
Sample code:
Dry run output:
What is the motivation / use case for changing the behavior?
Am I missing anything here? It worked like charm before and after I update packages it's not working anymore.
Environment
Deps:
Additional information:
I also tried the v1.0.0-beta.7 but it shows same results