Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
5.5(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
-
None
Description
Whenever creating a foreign key fails, the server reports something like
1005: Can't create table test.t3 (errno: 150 "Foreign key constraint is incorrectly formed")
|
which is not very informative. One can get a much better understanding of an error by issuing SHOW ENGINE INNODB STATUS, if one knows to do it.
But one shouldn't be required to. The error information should be returned when an error happens. For example, InnoDB could return a warning with, say, "There is no index in the referenced table where the referenced columns appear as the first columns" (may be slightly paraphrased, as appropriate for a warning message).
It could still do its SHOW ENGINE INNODB STATUS, but returning a warning goes a long way towards helping users to understand the problem
Attachments
Issue Links
- relates to
-
MDEV-16356 Allow ALGORITHM=NOCOPY for ADD CONSTRAINT
-
- Open
-
-
MDEV-16417 Store Foreign Key metadata outside of InnoDB
-
- In Review
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue relates to MDEV-16356 [ MDEV-16356 ] |
| Link | This issue relates to MDEV-16417 [ MDEV-16417 ] |
| Workflow | MariaDB v3 [ 96699 ] | MariaDB v4 [ 141287 ] |
I think that this should be addressed as part of MDEV-16417.
If ALTER TABLE is using the native algorithm (not ALGORITHM=COPY), then better messages could already be reported. But, until MDEV-16356 is fixed, ADD FOREIGN KEY will require ALGORITHM=COPY unless SET foreign_key_checks=0 is in effect.