Adding Identifying Relationship puts indices in wrong order
danielneri 4 years ago • updated by anonymous 4 years ago • 2
In MySQL, adding an identifying relationship places the new relationship at the first index of all keys on the table. MySQL doesn't like this since the auto increment id field needs to be in the first position. Have to reposition keys each time I add an identifying relationship. This is a newer bug.
MySQL Error: "Incorrect table definition; there can be only one auto column and it must be defined as a key"
Customer support service by UserEcho
We are looking into this issue. We will notify you as soon as we know more details.
Team - SqlDBM
Dear user, could you provide sharelink to your project, any screenshots with example?
This will help us quickly understand the problem and fix it.
Thank you for your assistance,