mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 20:42:30 +01:00
692fcba403
client/mysqltest.cc: Free mutex after usage (fixes valgrind warnings in embedded server) mysql-test/include/gis_keys.inc: Fixed failure in innodb.gis_test mysql-test/r/gis.result: Updated result mysql-test/suite/innodb/r/innodb_gis.result: Updated results mysql-test/suite/innodb/t/innodb_bug38231.test: Added handling of timeouts (happend on some servers in buildbot) mysql-test/suite/innodb_plugin/r/innodb_gis.result: Updated results mysql-test/suite/innodb_plugin/t/innodb.test: Use error names instead of numbers mysql-test/suite/innodb_plugin/t/innodb_misc1.test: This test requires utf8 mysql-test/suite/innodb_plugin/t/innodb_mysql.test: This test requires Xtradb sql/sql_base.cc: Don't print table names for placeholders. sql/sql_show.cc: Temporary fix: Save and restore db and table_name in mysqld_show_create (to get rid of valgrind warning) A better solution that needs to be investgated is to not change these fields in mysql_derived_prepare() sql/sql_view.cc: Fixed valgrind warning storage/xtradb/handler/ha_innodb.cc: Don't access THD directly
63 lines
2 KiB
SQL
63 lines
2 KiB
SQL
--source include/have_geometry.inc
|
|
|
|
#
|
|
# Spatial objects with keys
|
|
#
|
|
|
|
#
|
|
# Bug #30825: Problems when putting a non-spatial index on a GIS column
|
|
#
|
|
|
|
CREATE TABLE t1 (p POINT);
|
|
CREATE TABLE t2 (p POINT, INDEX(p));
|
|
INSERT INTO t1 VALUES (POINTFROMTEXT('POINT(1 2)'));
|
|
INSERT INTO t2 VALUES (POINTFROMTEXT('POINT(1 2)'));
|
|
|
|
# no index, returns 1 as expected
|
|
SELECT COUNT(*) FROM t1 WHERE p=POINTFROMTEXT('POINT(1 2)');
|
|
|
|
# with index, returns 1 as expected
|
|
# EXPLAIN shows that the index is not used though
|
|
# due to the "most rows covered anyway, so a scan is more effective" rule
|
|
EXPLAIN
|
|
SELECT COUNT(*) FROM t2 WHERE p=POINTFROMTEXT('POINT(1 2)');
|
|
SELECT COUNT(*) FROM t2 WHERE p=POINTFROMTEXT('POINT(1 2)');
|
|
|
|
# adding another row to the table so that
|
|
# the "most rows covered" rule doesn't kick in anymore
|
|
# now EXPLAIN shows the index used on the table
|
|
# and we're getting the wrong result again
|
|
INSERT INTO t1 VALUES (POINTFROMTEXT('POINT(1 2)'));
|
|
INSERT INTO t2 VALUES (POINTFROMTEXT('POINT(1 2)'));
|
|
EXPLAIN
|
|
SELECT COUNT(*) FROM t1 WHERE p=POINTFROMTEXT('POINT(1 2)');
|
|
SELECT COUNT(*) FROM t1 WHERE p=POINTFROMTEXT('POINT(1 2)');
|
|
|
|
--replace_column 9 #
|
|
EXPLAIN
|
|
SELECT COUNT(*) FROM t2 WHERE p=POINTFROMTEXT('POINT(1 2)');
|
|
SELECT COUNT(*) FROM t2 WHERE p=POINTFROMTEXT('POINT(1 2)');
|
|
|
|
EXPLAIN
|
|
SELECT COUNT(*) FROM t2 IGNORE INDEX(p) WHERE p=POINTFROMTEXT('POINT(1 2)');
|
|
SELECT COUNT(*) FROM t2 IGNORE INDEX(p) WHERE p=POINTFROMTEXT('POINT(1 2)');
|
|
|
|
DROP TABLE t1, t2;
|
|
|
|
--echo End of 5.0 tests
|
|
|
|
|
|
--echo #
|
|
--echo # Test for bug #58650 "Failing assertion: primary_key_no == -1 ||
|
|
--echo # primary_key_no == 0".
|
|
--echo #
|
|
--disable_warnings
|
|
drop table if exists t1;
|
|
--enable_warnings
|
|
--echo # The minimal test case.
|
|
create table t1 (a int not null, b linestring not null, unique key b (b(12)), unique key a (a));
|
|
drop table t1;
|
|
--echo # The original test case.
|
|
create table t1 (a int not null, b linestring not null, unique key b (b(12)));
|
|
create unique index a on t1(a);
|
|
drop table t1;
|