-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Fixed Magento installation with MySQL 8. #25357
Fixed Magento installation with MySQL 8. #25357
Conversation
Hi @akaplya. Thank you for your contribution
For more details, please, review the Magento Contributor Guide documentation. |
Hi @VladimirZaets, thank you for the review.
|
✔️ QA Passed |
@magento run all tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Hi @novikor, thank you for the review. |
Hi @akaplya, thank you for your contribution! |
Description (*)
Fixed Magneto installation with MySQL 8.
Fixed Issues (if relevant)
It was impossible to install Magento 2.3.3 with MySQL 8.
The cause of this issue was a forced indexation triggered by the DB patch.
The first time indexation may cause DDL scripts execution. At the same time, Magento wraps DB patches with the transaction.
As a result, Magento tries to open a new connection to perform DDL, and the original transaction does not see a table that created after the transaction started.
Reasonable workaround - do not invoke indexation from the patch. If necessary, the indexer can be invalidated.
This is a safe operation that does not require DDL execution and could be invoked from the patch.
Manual testing scenarios (*)
#25294
Contribution checklist (*)