summaryrefslogtreecommitdiff
path: root/mysql-test/t/gis.test
diff options
context:
space:
mode:
authorSergei Golubchik <serg@mariadb.org>2017-03-02 15:36:18 +0100
committerSergei Golubchik <serg@mariadb.org>2017-03-10 18:21:24 +0100
commit48b1d175345caa3c644597044751906a04106b91 (patch)
tree3dca0a0fda49aed13c12899a0bd5d5993d6f4607 /mysql-test/t/gis.test
parent25c32c89f14cba402a42a61a8a371ce515610899 (diff)
downloadmariadb-git-48b1d175345caa3c644597044751906a04106b91.tar.gz
MDEV-11943 I_S.TABLES inconsistencies with tables with unknown storage engine
Make SELECT <columns> FROM I_S.TABLES behave identically independently from whether <columns> require opening the table in engine or <columns> can be filled with only opening the frm. In particular, fill_schema_table_from_frm() should not silently skip frms with unknown engine, but should fill the I_S.TABLES row with NULLs just like fill_schema_table_by_open() does.
Diffstat (limited to 'mysql-test/t/gis.test')
-rw-r--r--mysql-test/t/gis.test4
1 files changed, 2 insertions, 2 deletions
diff --git a/mysql-test/t/gis.test b/mysql-test/t/gis.test
index 18cfe95b749..ea4c024988d 100644
--- a/mysql-test/t/gis.test
+++ b/mysql-test/t/gis.test
@@ -1460,12 +1460,12 @@ SHOW CREATE TABLE information_schema.spatial_ref_sys;
create table t1(g GEOMETRY, pt POINT);
create table t2(g LINESTRING, pl POLYGON);
-select * from information_schema.geometry_columns;
+select * from information_schema.geometry_columns where f_table_schema='test';
drop table t1, t2;
--echo 10.1 tests
create table t1(g GEOMETRY(9,4) REF_SYSTEM_ID=101, pt POINT(8,2), pg GEOMETRY REF_SYSTEM_ID=102);
-SELECT SRID from information_schema.geometry_columns WHERE G_TABLE_NAME='t1';
+SELECT SRID from information_schema.geometry_columns WHERE f_table_schema='test' and G_TABLE_NAME='t1';
drop table t1;
-- echo # Expect an int(1) column to be created