MDEV-29871 innodb_fts.fulltext_misc unexpectedly reports a result

- match()+0 returns the floating result and converts into integer value
and it leads to sporadic failure.
parent a474e327
...@@ -129,8 +129,9 @@ test ...@@ -129,8 +129,9 @@ test
select * from t1 where a like "te_t"; select * from t1 where a like "te_t";
a a
test test
select * from t1 where match a against ("te*" in boolean mode)+0; select * from t1 where match a against ("te*" in boolean mode);
a a
test
drop table t1; drop table t1;
# #
# Bug #49734: Crash on EXPLAIN EXTENDED UNION ... ORDER BY # Bug #49734: Crash on EXPLAIN EXTENDED UNION ... ORDER BY
......
...@@ -152,10 +152,7 @@ insert into t1 values ("a"),("abc"),("abcd"),("hello"),("test"); ...@@ -152,10 +152,7 @@ insert into t1 values ("a"),("abc"),("abcd"),("hello"),("test");
select * from t1 where a like "abc%"; select * from t1 where a like "abc%";
select * from t1 where a like "test%"; select * from t1 where a like "test%";
select * from t1 where a like "te_t"; select * from t1 where a like "te_t";
# InnoDB_FTS: we don't support the postfix "+0" select * from t1 where match a against ("te*" in boolean mode);
# Work around MDEV-29871 (FIXME: remove this)
--echo select * from t1 where match a against ("te*" in boolean mode)+0;
--echo a
drop table t1; drop table t1;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment