mariadb/mysql-test/suite/innodb_gis/t/bug17057168.test
Jan Lindström a6a4c25bf7 MariaDB adjustments to innodb_gis tests.
Some test are still disabled as they provide different results,
fail on different error or crash.

Fixes also MDEV-14060 InnoDB: Foreign key constraint to
geometry type does not work where test intentionally tried
incorrect cases.
2017-10-25 06:47:08 +03:00

33 lines
1.2 KiB
Text

#********************************************************
# Bug 17057168 - LARGE PERFORMANCE REGRESSION FOR INNODB
# GEOMETRY/SPATIAL INDEX LOOKUP
#********************************************************
--source include/have_geometry.inc
--source include/not_embedded.inc
--source include/no_valgrind_without_big.inc
--source include/have_innodb.inc
CREATE DATABASE geotest;
use geotest;
CREATE TABLE tmp (id int unsigned NOT NULL PRIMARY KEY);
INSERT INTO tmp VALUES (0), (1), (2), (3), (4), (5), (6), (7), (8), (9);
INSERT INTO tmp SELECT 10+id FROM tmp;
INSERT INTO tmp SELECT 20+id FROM tmp;
INSERT INTO tmp SELECT 40+id FROM tmp;
INSERT INTO tmp SELECT 80+id FROM tmp;
CREATE TABLE t1 (id int unsigned NOT NULL auto_increment PRIMARY KEY,
location point, INDEX (location)) ENGINE=InnoDB;
INSERT INTO t1 (location) SELECT POINT(tmp1.id, tmp2.id) FROM tmp tmp1,
tmp tmp2 ORDER BY tmp1.id, tmp2.id;
#Befor fix, the row number will be the total number of index recs,
#After fix, the row number will be 1.
EXPLAIN SELECT id, ST_AsText(location) FROM t1 WHERE location = POINT(1,
2);
SELECT id, ST_AsText(location) FROM t1 WHERE location = POINT(1, 2);
DROP TABLE t1;
DROP TABLE tmp;
DROP DATABASE geotest;