File: innodb_gis.test

package info (click to toggle)
mariadb-10.3 1%3A10.3.34-0%2Bdeb10u1
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 531,600 kB
  • sloc: cpp: 1,415,326; ansic: 917,243; perl: 58,570; sh: 43,538; pascal: 39,206; java: 33,919; yacc: 32,096; javascript: 15,655; python: 10,576; ruby: 8,684; xml: 5,957; makefile: 4,893; sql: 3,750; asm: 841; lex: 670; php: 22; awk: 20; sed: 16
file content (22 lines) | stat: -rw-r--r-- 718 bytes parent folder | download 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
--source include/have_innodb.inc
SET storage_engine=innodb;
--source include/gis_generic.inc
--source include/gis_keys.inc

#
# Bug #15680 (SPATIAL key in innodb)
#
# MySQL 5.7 Introduces SPATIAL keys for InnoDB
#--error ER_TABLE_CANT_HANDLE_SPKEYS
create table t1 (g geometry not null, spatial gk(g)) engine=innodb;
drop table t1;

#
# MDEV-12462 SPATIAL index fails to work with CONTAINS
#

create table t1(id int not null primary key, g1 geometry not null, spatial index(g1));
insert into t1 values(1, polygonfromtext('POLYGON((0 0, 0 5, 5 5, 5 0, 0 0))'));
explain select id from t1 where contains(g1, pointfromtext('POINT(1 1)'));
select id from t1 where contains(g1, pointfromtext('POINT(1 1)'));
drop table t1;