-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Propel repeatedly generating the same migrations in subsequent diffs. #1031
Comments
I am also experiencing the same issue. I am always getting this inserted into my migrations: ALTER TABLE CHANGE The field is longvarchar in the schema and live database.. |
Which version do you use? Is this also the case for current 2.0.0-alpha5 (not |
For me, this happened in both dev-master and 2.0.0-alpha5 composer.lock for 2.0.0-alpha5
composer.lock for dev-master
|
You could remove |
@SourceCode please shouw us your schema.xml. Guess you have specified a |
Marc - |
Removing the size property fixed the issue. Still a small bug. |
Is this still relevant or can it be closed? |
Can be closed. |
Propel is repeatedly generating the same diff over and over regardless of whether or not I run the migration.
The columns appear to always be integers.
They're all non nullable columns.
Some are auto increment.
Here's a model that is generating the diff, despite not being different:
The SQL Create Table statement (generated from MySQL workbench)
Just as a side note, the bug doesn't prevent me from doing any work -- it just adds unnecessary queries (that do nothing in the end) to my migrations.
The query that gets generated in the migration is:
The text was updated successfully, but these errors were encountered: