File: innodb_gis.test

package info (click to toggle)
mariadb 1%3A11.8.3-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 772,520 kB
  • sloc: ansic: 2,414,714; cpp: 1,791,394; asm: 381,336; perl: 62,905; sh: 49,647; pascal: 40,897; java: 39,363; python: 20,791; yacc: 20,432; sql: 17,907; xml: 12,344; ruby: 8,544; cs: 6,542; makefile: 6,145; ada: 1,879; lex: 1,193; javascript: 996; objc: 80; tcl: 73; awk: 46; php: 22
file content (22 lines) | stat: -rw-r--r-- 726 bytes parent folder | download | duplicates (5) 
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 default_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;