Skip to content

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

Merged
merged 1 commit into from
Apr 16, 2018
Merged

magento/magento2#14465 Fix empty changelog tables after MySQL restart. #14471

merged 1 commit into from
Apr 16, 2018

Conversation

swnsma
Copy link
Contributor

@swnsma swnsma commented Mar 30, 2018

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)

Leave at least one record after tebles cleanup.
@swnsma swnsma added partners-contribution Pull Request is created by Magento Partner Partner: ISM eCompany Pull Request is created by partner ISM eCompany Release Line: 2.1 labels Mar 30, 2018
@sidolov sidolov requested review from ihor-sviziev and removed request for ihor-sviziev April 6, 2018 08:43
@sidolov
Copy link
Contributor

sidolov commented Apr 11, 2018

Hi @swnsma , please, create PR with the same changes to 2.2-develop branch firstly, after that we can proceed with current. Thanks!

@ihor-sviziev
Copy link
Contributor

ihor-sviziev commented Apr 11, 2018

Hi @sidolov,
I already created PRs to 2.2-develop #14635 and 2.3-develop #14636 branches

@magento-engcom-team magento-engcom-team added this to the April 2018 milestone Apr 11, 2018
@toddbc
Copy link
Contributor

toddbc commented Apr 14, 2018

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.)

@ihor-sviziev
Copy link
Contributor

@toddbc sorry for not processing your PRs, they seemed to me as fix in not optimal way

@magento-engcom-team
Copy link
Contributor

Hi @swnsma. Thank you for your contribution.
Changes from your Pull Request will be available with the upcoming 2.1.15 release.

@toddbc
Copy link
Contributor

toddbc commented Apr 16, 2018

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Partner: ISM eCompany Pull Request is created by partner ISM eCompany partners-contribution Pull Request is created by Magento Partner Progress: accept Progress: on hold Release Line: 2.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants