-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Database Schema: Missing important Foreign Keys #1001
Comments
SchumacherFM
changed the title
Database Schema: Missing important Foreign Keys and incorrect Unique Indexes
Database Schema: Missing important Foreign Keys
Jan 27, 2015
Few of keys you mentioned were identified as unused with http://www.percona.com/doc/percona-toolkit/2.1/pt-duplicate-key-checker.html and thus eliminated. |
@SchumacherFM There are two main reasons why we removed such keys:
Do you have any additional questions? |
Thank you for answering! |
magento-engcom-team
added a commit
that referenced
this issue
Oct 22, 2019
…ver\CreateCustomerAddress #1001 - Merge Pull Request magento/graphql-ce#1001 from TomashKhamlai/graphql-ce:coverage-create-customer-address-input - Merged commits: 1. f1e8568
magento-engcom-team
pushed a commit
that referenced
this issue
Oct 22, 2019
…ver\CreateCustomerAddress #1001
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During my database schema comparison I discovered several missing foreign keys and one incorrect unique index (at least I think the unique key is wrong 8-) Issue #1002 ).
The following 5 screenshots shows the missing keys. Left side Magento2 and right side Magento1.
If there is a technical reason why you haven't implemented the keys: Please explain :-)
The text was updated successfully, but these errors were encountered: