Bug #80271 Generated columns are required in INSERT INTO ... SELECT * FROM ... commands

Description:
MySQL requires supplying a (dummy) value for generated columns in INSERT INTO ... SELECT ... FROM command.

How to repeat:
CREATE TABLE `asource` (
  `id` int(10) unsigned NOT NULL DEFAULT '0'
);

CREATE TABLE `adestination` (
  `id` int(10) unsigned NOT NULL DEFAULT '0',
  `generated` tinyint(1) GENERATED ALWAYS AS (id = 2) STORED NOT NULL
);

INSERT INTO adestination 
SELECT asource.* FROM asource;

Suggested fix:
As generated columns are generated and could not be manually assigned a value, they should not be required to mention in INSERT INTO ... SELECT ... FROM command (but might be as if the asource has the generated column, it will be included and its value should be silently skipped).

Raised Severity as #79204 in 5.7.11 made the thing worse (#80293).

A workaround to provide some value to that generated column no longer works. The DEFAULT is not syntactically supported for INSERT INTO ... SELECT * FROM ... statement.

Fixed title.

Thank you for the report.
Marking this as duplicate of Bug #80293.