Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.4.6, 10.3(EOL), 10.4(EOL)
Description
Steps to reproduce:
MariaDB [sbtest]> show create table sbtest1\G |
*************************** 1. row ***************************
|
Table: sbtest1 |
Create Table: CREATE TABLE `sbtest1` ( |
`id` int(11) NOT NULL AUTO_INCREMENT, |
`k` int(11) NOT NULL DEFAULT 0, |
`c` char(120) NOT NULL DEFAULT '', |
`pad` char(60) NOT NULL DEFAULT '', |
PRIMARY KEY (`id`), |
KEY `k_1` (`k`) |
) ENGINE=InnoDB AUTO_INCREMENT=220753785 DEFAULT CHARSET=latin1 |
1 row in set (0.001 sec) |
 |
MariaDB [sbtest]> alter table sbtest1 add system versioning; |
Query OK, 114979 rows affected (29.251 sec) |
Records: 114979 Duplicates: 0 Warnings: 0
|
Trying to add column:
MariaDB [sbtest]> alter table sbtest1 add column row_start TIMESTAMP(6) AS ROW START INVISIBLE; |
ERROR 4124 (HY000): Table `sbtest1` is not system-versioned |
Not True as this table is already system-versioned.
Column description was grabbed from:
https://mariadb.com/kb/en/library/temporal-data-tables/#using-bitemporal-tables
Attachments
Issue Links
- is duplicated by
-
MDEV-16130 wrong error message adding AS ROW START to versioned table
- Closed