-
Notifications
You must be signed in to change notification settings - Fork 9.4k
magento/magento2#14465 Fix empty changelog tables after MySQL restart. #14471
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
magento/magento2#14465 Fix empty changelog tables after MySQL restart. #14471
Conversation
Leave at least one record after tebles cleanup.
Hi @swnsma , please, create PR with the same changes to 2.2-develop branch firstly, after that we can proceed with current. Thanks! |
Note: this is essentially the same as #13577, although I played it safe in case of other callers. That should be closed once this is merged, assuming this will be merged instead (my 2.2 and 2.3 PRs were ignored as well.) |
@toddbc sorry for not processing your PRs, they seemed to me as fix in not optimal way |
Hi @swnsma. Thank you for your contribution. |
@ihor-sviziev happy to hear feedback. Probably better to say that on the PR than just radio silence. Multiple people in the community hit this bug in the meantime - it could've been fixed sooner. Although, I'd argue that a single extra SQL query to validate the parameter for something run once a day is not going to break the bank. Most of my PRs (including recent ones) have been to fix major performance issues, so I definitely care about performance. |
Leave at least one record after tebles cleanup.
Description
This pull request is related to the issue #14465.
The idea of the fix - leave at least one record in changelog tables.
So after restart of MySQL, tables will never by empty.
Fixed Issues (if relevant)
Manual testing scenarios
The test scenario is well described in the issue.
Contribution checklist