-
Notifications
You must be signed in to change notification settings - Fork 111
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
Upgrade to 103.4.53 caused UPDATE on over 60% of the existing (old) orders #1772
Closed
Milestone
Comments
lbajsarowicz
changed the title
Upgrade to 103.4.53 caused UPDATE on 80.000 orders
Upgrade to 103.4.53 caused UPDATE on over 60% of the existing (old) orders
Aug 17, 2023
This caused issues for several of our customers when deploying to production. |
gonzaloebiz
added a commit
that referenced
this issue
Aug 21, 2023
gonzaloebiz
added a commit
that referenced
this issue
Aug 21, 2023
gonzaloebiz
added a commit
that referenced
this issue
Aug 21, 2023
gonzaloebiz
added a commit
that referenced
this issue
Aug 21, 2023
This was
linked to
pull requests
Aug 21, 2023
gonzaloebiz
added a commit
that referenced
this issue
Aug 22, 2023
closes #1772 for magento 2.3.6-p1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
My Client has 130.000 orders in their store. As Mailchimp official extension is full of bugs, I decided to upgrade the extension from
103.4.51
to103.4.53
, which is considered a patch version, thus should not introduce any backwards incompatible changes.The Data Patch introduced in the scope of release
https://github.com/mailchimp/mc-magento2/blob/develop-2.4/Setup/Patch/Data/Migrate452.php
Caused update of
80000
out of130000
orders in the database. As a result, the ERP synchronization queue is already stuck for 2 days.Preconditions
Steps to reproduce
A/A
Actual and Expected result
Additional information
When you introduce changes that affect existing data in the database:
The text was updated successfully, but these errors were encountered: