Migration problems with a legacy demoshop using mysql after updating modules

jochen.gartner
jochen.gartner Posts: 42 🧑🏻‍🚀 - Cadet
edited June 2023 in Propel ORM

Hello everyone! We have propel migration problems with a legacy demoshop using mysql after updating a lot of modules.

Tagged:

Best Answer

  • jochen.gartner
    jochen.gartner Posts: 42 🧑🏻‍🚀 - Cadet
    Answer ✓

    turned out to be a bug or mysql incompatibilty in spryker's synchronizationBehavior, had to override on project level.

Answers

  • jochen.gartner
    jochen.gartner Posts: 42 🧑🏻‍🚀 - Cadet

    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?

  • jochen.gartner
    jochen.gartner Posts: 42 🧑🏻‍🚀 - Cadet
  • jochen.gartner
    jochen.gartner Posts: 42 🧑🏻‍🚀 - Cadet
    Answer ✓

    turned out to be a bug or mysql incompatibilty in spryker's synchronizationBehavior, had to override on project level.

Categories