[update] enhance performance on large catalog - #16570
magento-engcom-team merged 4 commits into
Conversation
|
Hi @AurelienLavorel. Thank you for your contribution
For more details, please, review the Magento Contributor Assistant documentation |
|
Related Pull Request: |
|
Hi @ihor-sviziev, thank you for the review. |
|
Result query will be following: UPDATE sales_order_address
INNER JOIN sales_order ON sales_order_address.parent_id = sales_order.entity_id
INNER JOIN quote_address ON sales_order.quote_id = quote_address.quote_id
AND sales_order_address.address_type = quote_address.address_type
SET sales_order_address.quote_address_id = quote_address.address_id
WHERE sales_order_address.quote_address_id IS NULL |
|
Hi @AurelienLavorel. Thank you for your contribution. Please, consider to port this solution to 2.3 release line. |
|
@magento-engcom-team this patch won't work with Enterprise Edition with split database setup. |
|
Hi @rikwillems, |
|
Hi @AurelienLavorel, In such configuration we have 2 split databases
Could you prepare new PR that fixing this issue OR revert your changes? |
|
Yes, I'm mounting an environment with that set up to try. |
|
Hi @AurelienLavorel, |
|
@ihor-sviziev Please see my PR as a fix for this issue. |

Description
On Magento update, if you have a big number of order (>100k for my case), you can't pass setup:upgrade step.
Instead of using Magento collection, it's a direct SQL request.
Manual testing scenarios
Upgrade Magento from 2.2.2 to 2.2.5.
Contribution checklist