Hello everyone! We have propel migration problems with a legacy demoshop using mysql after updating a lot of modules.
turned out to be a bug or mysql incompatibilty in spryker's synchronizationBehavior, had to override on project level.
So, we are currently applying updates to an outdated legacy demoshop (last updated august 2018) running mysql instead of postgres. At some point during the update process we realized that propel:diff suddenly does weird things, see appended migration. This removing and re-applying of indexes happens with each run of propel:diff even if we propel:migrate afterwards. Has anyone come across this? Any idea what to check?
turned out to be a bug or mysql incompatibilty in spryker's synchronizationBehavior, had to override on project level.