[wp-trac] [WordPress Trac] #44384: InnoDB doesn't support SPATIAL indexes for query CREATE TEMPORARY TABLE

WordPress Trac noreply at wordpress.org
Mon Aug 6 17:58:44 UTC 2018


#44384: InnoDB doesn't support SPATIAL indexes for query CREATE TEMPORARY TABLE
--------------------------+-----------------------------
 Reporter:  ottok         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Database      |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+-----------------------------

Comment (by ottok):

 Looks fine here:
 {{{
 +--------------------+
 | version()          |
 +--------------------+
 | 10.3.9-MariaDB-log |
 +--------------------+
 1 row in set (0.000 sec)

 MariaDB [test]> CREATE TEMPORARY TABLE wptests_spatial_index_test
 (non_spatial bigint(20) unsigned NOT NULL,spatial_value geometrycollection
 NOT NULL,KEY non_spatial (non_spatial),SPATIAL KEY spatial_key
 (spatial_value)) ENGINE=MyISAM;
 Query OK, 0 rows affected (0.001 sec)

 MariaDB [test]> CREATE TEMPORARY TABLE wptests_spatial_index_test2
 (non_spatial bigint(20) unsigned NOT NULL,spatial_value geometrycollection
 NOT NULL,KEY non_spatial (non_spatial),SPATIAL KEY spatial_key
 (spatial_value)) ENGINE=Innodb;
 Query OK, 0 rows affected (0.001 sec)

 MariaDB [test]> set global enforce_storage_engine='InnoDB';
 Query OK, 0 rows affected (0.000 sec)

 MariaDB [test]> show global variables like '%engine%';
 +----------------------------+--------+
 | Variable_name              | Value  |
 +----------------------------+--------+
 | default_storage_engine     | InnoDB |
 | default_tmp_storage_engine |        |
 | enforce_storage_engine     | InnoDB |
 | gtid_pos_auto_engines      |        |
 | storage_engine             | InnoDB |
 +----------------------------+--------+
 5 rows in set (0.002 sec)

 MariaDB [test]> CREATE TEMPORARY TABLE wptests_spatial_index_test3
 (non_spatial bigint(20) unsigned NOT NULL,spatial_value geometrycollection
 NOT NULL,KEY non_spatial (non_spatial),SPATIAL KEY spatial_key
 (spatial_value)) ENGINE=MyISAM;
 }}}


 The only place ER_TABLE_CANT_HANDLE_SPKEYS happens in innodb seems to be
 in an online ALTER TABLE.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44384#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list