359
359
# Expected result is 36.3310176346905, but IA64 returns 36.3310176346904
360
360
# due to fused multiply-add instructions.
361
--replace_result 36.3310176346904 36.3310176346905
361
--replace_result 36.3310176346904 36.3310176346905 -114.87787186923326 -114.87787186923313 36.33101763469053 36.33101763469059 36.33101763469043 36.33101763469059
362
362
select object_id, geometrytype(geo), ISSIMPLE(GEO), ASTEXT(centroid(geo)) from
363
363
t1 where object_id=85984;
744
744
SET @a=POLYFROMWKB(@a);
748
# Bug #57321 crashes and valgrind errors from spatial types
751
create table t1(a polygon NOT NULL)engine=myisam;
752
insert into t1 values (geomfromtext("point(0 1)"));
753
insert into t1 values (geomfromtext("point(1 0)"));
754
select * from (select polygon(t1.a) as p from t1 order by t1.a) d;
759
--echo # Test for bug #59888 "debug assertion when attempt to create spatial index
760
--echo # on char > 31 bytes".
762
create table t1(a char(32) not null) engine=myisam;
763
--error ER_WRONG_ARGUMENTS
764
create spatial index i on t1 (a);
769
# Bug#11767480 - SPATIAL INDEXES ON NON-SPATIAL COLUMNS CAUSE CRASHES.
771
CREATE TABLE t0 (a BINARY(32) NOT NULL);
772
--error ER_WRONG_ARGUMENTS
773
CREATE SPATIAL INDEX i on t0 (a);
774
INSERT INTO t0 VALUES (1);
776
--error ER_WRONG_ARGUMENTS
778
col0 BINARY NOT NULL,
780
SPATIAL INDEX i1 (col0)
783
# Test other ways to add indices
785
col0 BINARY NOT NULL,
789
--error ER_WRONG_ARGUMENTS
790
CREATE SPATIAL INDEX idx0 ON t1(col0);
792
--error ER_WRONG_ARGUMENTS
793
ALTER TABLE t1 ADD SPATIAL INDEX i1 (col0);
796
col0 INTEGER NOT NULL,
801
--error ER_WRONG_ARGUMENTS
802
CREATE SPATIAL INDEX idx0 ON t2 (col1, col2);
804
--error ER_WRONG_ARGUMENTS
806
col0 INTEGER NOT NULL,
809
SPATIAL INDEX i1 (col1, col2)
813
DROP TABLE t0, t1, t2;
747
815
--echo End of 5.1 tests