[Forwardport] magento/magento2#14465 Fix empty changelog tables after MySQL restart.#14635
Merged
magento-engcom-team merged 1 commit intomagento:2.2-developfrom Apr 14, 2018
Conversation
…t least one record after tebles cleanup.
4 tasks
sidolov
approved these changes
Apr 12, 2018
Contributor
|
Hi @sidolov, thank you for the review. |
Contributor
|
Hi @ihor-sviziev. Thank you for your contribution. |
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Original Pull Request
#14471
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