Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL)
-
None
Description
--source suite/federated/have_federatedx.inc
|
|
|
create table t (a int, b int as (a)); |
--eval create table tf connection 'mysql://root@127.0.0.1:$MASTER_MYPORT/test/t' engine=Federated
|
|
|
show create table tf; |
|
|
# Cleanup
|
drop table tf, t; |
In the test case above, the table is created without errors or warnings, but then any action on this table fails with ER_UNSUPPORTED_ENGINE_FOR_GENERATED_COLUMNS:
|
10.3 730eb1c4 |
mysqltest: At line 6: query 'show create table tf' failed: 1910: FEDERATED storage engine does not support generated columns |
The unpleasant (and possibly realistic) side-effect is that such tables break mysqldump and some queries from INFORMATION_SCHEMA.