[MDEV-29423] Incorrect bindings depending on full text search term Created: 2022-08-31  Updated: 2023-11-28

Status: Confirmed
Project: MariaDB Server
Component/s: Full-text Search, Storage Engine - InnoDB
Affects Version/s: 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9
Fix Version/s: 10.4, 10.5, 10.6

Type: Bug Priority: Major
Reporter: Alex Dawn Assignee: Thirunarayanan Balathandayuthapani
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Windows 10
laravel/lumen-framework: 5.8
10.8.3-MariaDB


 Description   

With Maria 10.8.3 I am getting the same issue that was reported here: https://bugs.mysql.com/bug.php?id=78485

Without boolean mode, the bindings are working as expected, but with bindings the quoting of the search term by the engine are not there when certain symbols are in the term.

 Comments   
Comment by Alice Sherepa [ 2022-11-10 ]

Thanks! I repeated on 10.3-10.10

--source include/have_innodb.inc 
 
 
CREATE TABLE t1(a TEXT CHARACTER SET LATIN1, FULLTEXT INDEX(a)) ENGINE=myisam;
 
insert into t1 values ('a'),('b');
 
 
 
SELECT * FROM t1 WHERE MATCH(a) AGAINST("*");
 
alter table t1 engine=innodb;
 
 
 
###--error :
 
 
 
SELECT * FROM t1 WHERE MATCH(a) AGAINST("*");

this test is also present in innodb_fts_misc.test and innodb_fts/t/fulltext.test

Generated at Thu Feb 08 10:08:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.