Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.6.14
-
None
Description
When doing a backup of a table with a virtual colum (GENERATED ALWAYS) the mysqldump tools fails to see its a generated column and adds it to the restore
example
CREATE TABLE example( |
firstname VARCHAR(255), |
lastname VARCHAR(255), |
fullname VARCHAR(512) AS (CONCAT(firstname, ' ', lastname)) VIRTUAL |
);
|
 |
insert into example(firstname, lastname) values('Donald', 'Duck'); |
then a mysqldump --opt generates
LOCK TABLES `example` WRITE;
|
/*!40000 ALTER TABLE `example` DISABLE KEYS */; |
INSERT INTO `example` VALUES ('Donald','Duck','Donald Duck'); |
/*!40000 ALTER TABLE `example` ENABLE KEYS */; |
UNLOCK TABLES;
|
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; |
It should actually ignore it since its generated.
The example above is very simple but we have seen issues with restoring due to this.
Attachments
Issue Links
- is part of
-
MDEV-28906 MySQL 8.0 desired compatibility
- Open
- links to