Skip to content
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

[Forwardport] magento/magento2#14465 Fix empty changelog tables after MySQL restart. #14635

Conversation

ihor-sviziev
Copy link
Contributor

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)

  1. [Indexes] Product 'version_id' lost last 'auro_increment' value after MySQL restart. #14465: Indexes] Product 'version_id' lost last 'auro_increment' value after MySQL restart.

Manual testing scenarios

The test scenario is well described in the issue.

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

@magento-engcom-team
Copy link
Contributor

Hi @sidolov, thank you for the review.
ENGCOM-1260 has been created to process this Pull Request

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev. Thank you for your contribution.
Changes from your Pull Request will be available with the upcoming 2.2.5 release.

@ihor-sviziev ihor-sviziev deleted the 2.2-develop-PR-port-14471 branch April 16, 2018 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants