Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3(EOL)
-
None
Description
As analysis for MDEV-14789 says, there were two ways to handle it – either disable the combination, or fix it. What happened at the end is that SELECT works, but neither table discovery nor data modification do. So, all in all, probably it makes sense to disable it.
Discovery:
create or replace table t3 (a int) with system versioning; |
create or replace table t3f engine=Federated CONNECTION='mysql://root@127.0.0.1:3306/test/t3' ; |
10.3 c39f8a80c9fe7 |
MariaDB [test]> create or replace table t3f engine=Federated CONNECTION='mysql://root@127.0.0.1:3306/test/t3' ; |
ERROR 1939 (HY000): Engine FEDERATED failed to discover table `test`.`t3f` with 'CREATE TABLE `t3` ( |
`a` int(11) DEFAULT NULL
|
) WITH SYSTEM VERSIONING CONNECTION='mysql://root@127.0.0.1:3306/test/t3'' |
DML:
create or replace table t3f (a int) engine=Federated CONNECTION='mysql://root@127.0.0.1:3306/test/t3' with system versioning; |
insert into t3f (a) values (1); |
MariaDB [test]> insert into t3f (a) values (1); |
ERROR 1296 (HY000): Got error 10000 'Error on remote system: 1054: Unknown column 'row_start' in 'field list'' from FEDERATED |
Attachments
Issue Links
- is blocked by
-
MDEV-16157 federated corrupts timestamps
- Closed
- relates to
-
MDEV-29829 System versioning does not work with federation-like engines - disable if not supported
- Open