File: phrase.test

package info (click to toggle)
mariadb 1%3A11.8.3-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 772,520 kB
  • sloc: ansic: 2,414,714; cpp: 1,791,394; asm: 381,336; perl: 62,905; sh: 49,647; pascal: 40,897; java: 39,363; python: 20,791; yacc: 20,432; sql: 17,907; xml: 12,344; ruby: 8,544; cs: 6,542; makefile: 6,145; ada: 1,879; lex: 1,193; javascript: 996; objc: 80; tcl: 73; awk: 46; php: 22
file content (39 lines) | stat: -rw-r--r-- 1,029 bytes parent folder | download | duplicates (4) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
 
-- source include/have_innodb.inc

#
# BUG#20465273 - FULLTEXT SEARCH BEHAVIOUR WITH MYISAM VS. INNODB (WRONG RESULT WITH INNODB)
#

CREATE TABLE articles (
	id INT UNSIGNED AUTO_INCREMENT NOT NULL PRIMARY KEY,
	title VARCHAR(200),
	body TEXT,
	FULLTEXT (title,body)
) ENGINE=InnoDB;

INSERT INTO articles (title,body) VALUES
	(NULL, 'mysql good database'),
	(NULL, ' mysql good database'),
	('', 'mysql good database'),
	('', ' mysql good database'),
	(' ', 'mysql good database'),
	('mysql', 'good database'),
	('mysql ', 'good database'),
	('mysql', ' good database'),
	('mysql good database', ''),
	('mysql good database', NULL);


SET GLOBAL innodb_ft_aux_table="test/articles";
SELECT * FROM INFORMATION_SCHEMA.INNODB_FT_INDEX_CACHE;
SET GLOBAL innodb_ft_aux_table=default;

SELECT * FROM articles;

SELECT * FROM articles WHERE MATCH(title, body)
	AGAINST('"mysql good database"' IN BOOLEAN MODE);

SELECT * FROM articles WHERE MATCH(title, body)
	AGAINST('("mysql good database")' IN BOOLEAN MODE);

DROP TABLE articles;