-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Add unique key on eav_attribute_option_value table #28796
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
Add unique key on eav_attribute_option_value table #28796
Conversation
Hi @ihor-sviziev. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. |
(cherry picked from commit 502146f)
ce15dd0
to
eb05a10
Compare
@magento run all tests |
Pull Request state was updated. Re-review required.
Semantic Version Checker failed because of Unique key was added. It needs to approve. |
Seems like this is big change, we need to accept it in 2.5 release line |
Approval ticket - https://jira.corp.magento.com/browse/MC-37068 |
We have got the approval for our approval JIRA for Semantic Version Checker failure. Moving it to back to Ready for testing to get the latest code merge and get the QA done again. Thank you! |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
@magento run Functional Tests B2B , Functional Tests CE |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
@magento run WebAPI Tests,Unit Tests,Static Tests,Integration Tests,Functional Tests B2B |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
@magento run Unit Tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
@magento run Functional Tests B2B |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues. |
Functional Tests B2B failure are different on last two run on same commit. We have got the approval for our approval JIRA for |
This PR re-adds changes from #24720 after they were reverted due to missing approval for backward incompatible changes.
Description (*)
I believe we SHOULD add this index even if it's backward incompatible change as duplicated data in this table causing a lot of issues, we're having report page when trying to load attribute option values, explanation is here:

#24718 (comment)
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)