Skip to content
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

Update from 4.1.12 to 4.2.3 is incompatible with MySQL #139

Open
Pequem opened this issue Jul 30, 2021 · 2 comments
Open

Update from 4.1.12 to 4.2.3 is incompatible with MySQL #139

Pequem opened this issue Jul 30, 2021 · 2 comments

Comments

@Pequem
Copy link

Pequem commented Jul 30, 2021

Summary

The RemoveWorkflowAwareEntitiesQuery class in the Oro\Bundle\WorkflowBundle\Migration namespace is called in Oro\Bundle\CheckoutBundle\Migrations\Schema\v1_12\RemoveAlternativeCheckoutWorkflow Migration, but this class has a "CAST(wi.entity_id as integer)" in the Select Statement, but Mysql doesnt has support of integer type.

Steps to reproduce

Try to update oro application from 4.1.12 to 4.2.3

Actual Result

CheckoutBundle migration fails

Expected Result

CheckoutBundle migration must execute without error

Details about your environment

  • OroCommerce version: 4.2.3
  • PHP version: 7.4.21
  • Database (MySQL, PostgreSQL) version: MySQL 8

Additional information
I converted my database from MySQL to Postgres and the upgrade worked, then the problem is MySQL compatibility.

@XaBe20
Copy link

XaBe20 commented Mar 9, 2022

Same issue : #131

@chrisaligent
Copy link
Contributor

This was fixed in 5.0.2:
https://github.com/oroinc/orocommerce-application/releases/tag/5.0.2

* Syntax error produced by RemoveAlternativeCheckoutWorkflow migration when upgrading to 4.2 [BB-20466]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants