Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL)
-
None
Description
error after POINT, POLYGON, etc.
--source include/have_innodb.inc
|
--source include/have_sequence.inc
|
|
|
INSTALL SONAME 'ha_federatedx'; |
eval CREATE SERVER fedlink FOREIGN DATA WRAPPER mysql OPTIONS (USER 'root', HOST '127.0.0.1', DATABASE 'test', PORT $MASTER_MYPORT); |
|
CREATE TABLE t ( a linestring); |
CREATE TABLE t_fed ENGINE=FEDERATED CONNECTION='fedlink/t'; |
|
show create table t_fed; |
|
DROP TABLE t_fed, t; |
UNINSTALL SONAME 'ha_federatedx'; |
query 'CREATE TABLE t_fed ENGINE=FEDERATED CONNECTION='fedlink/t'' failed: ER_SQL_DISCOVER_ERROR (1939): Engine FEDERATED failed to discover table `test`.`t_fed` with 'CREATE TABLE `t` (
|
`a` linestring DEFAULT NULL
|
) CONNECTION='fedlink/t''
|
Should it be documented currently as a limitation in FederatedX?
It is a limitation of FederatedX, it does not support GEOMETRY columns. Such tables cannot be created explicitly and discovery fails too.
Technically, ha_federatedx::table_flags() is
{| HA_REC_NOT_IN_SEQ | HA_AUTO_PART_KEY | HA_CAN_INDEX_BLOBS |HA_BINLOG_ROW_CAPABLE | HA_BINLOG_STMT_CAPABLE | HA_CAN_REPAIR |HA_PRIMARY_KEY_REQUIRED_FOR_DELETE |HA_PARTIAL_COLUMN_READ | HA_NULL_IN_KEY);}which does not include HA_CAN_GEOMETRY