Bug #18651
closed
Extension Manager does not recognize more than one foreign key
0%
Description
When installing an extension, the extension manager, when creating the databse tables, does not recognize more than one foreign key per table.
(issue imported from #M8175)
Updated by Steffen Kamper about 16 years ago
can you give an example please? Any existing extension where this problem occurs?
Updated by Lucas about 16 years ago
Here you go:
CREATE TABLE tableWithForeignKeys (
field1 int(11) NOT NULL,
field2 int(11) NOT NULL,
FOREIGN KEY (field1) REFERENCES otherTable(field1) ON DELETE CASCADE,
FOREIGN KEY (field2) REFERENCES anotherTable(field2) ON DELETE CASCADE
) ENGINE=INNODB;
This is read by the EM in the following way:
CREATE TABLE tableWithForeignKeys (
field1 int(11) NOT NULL,
field2 int(11) NOT NULL,
FOREIGN KEY (field2) REFERENCES anotherTable(field2) ON DELETE CASCADE
) TYPE=INNODB;
And there is no extension I know of that has this problem. I've had this problem when writing an extension of my own.
Updated by Anja Leichsenring over 11 years ago
- Status changed from New to Resolved
- Target version deleted (
0)
Resolved with #17160.
Updated by