Re: Regarding "[Warning] InnoDB: Cannot add field"
Please pardon my bluntness---the table design is a recipe for performance disaster, so I'm relieved MySQL5.7 refuses to go along with it.
So does MySQL 8.0. As a rule of thumb, more than a hundred columns/table indicates serious design issues till proved otherwise.
May I suggest an alternative along these lines ...
CREATE TABLE `testcase` (
`id` bigint unsigned primary key auto_increment,
`phnareacode` varchar(32) DEFAULT NULL COMMENT '_extra',
`devid` bigint unsigned DEFAULT NULL COMMENT '_extra',
`second_id`int unsigned NOT NULL COMMENT '_extra',
);
CREATE TABLE testcase_details(
id bigint unsigned primary key auto_increment,
parentid bigint unsigned,
foreign key(parentid) references testcase(id)
on delete cascade on update cascade,
idx enum( col0 ... col233)
text text
);
Subject
Views
Written By
Posted
7519
July 27, 2021 04:24PM
2989
July 27, 2021 07:51PM
2278
July 29, 2021 11:40AM
1607
July 29, 2021 12:17PM
1684
August 02, 2021 01:09PM
Re: Regarding "[Warning] InnoDB: Cannot add field"
1778
August 02, 2021 03:17PM
1553
August 02, 2021 06:18PM
1773
August 02, 2021 11:47PM
1531
August 03, 2021 07:34PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.