hmm ... adding a few rows not matching the word seems to help in my test DB. Now I found out how the 50% rule works.
INSERT INTO `matchtest` VALUES ('5', 'nofind 1', 'nothing');
INSERT INTO `matchtest` VALUES ('6', 'nofind 2', 'old as stone');
INSERT INTO `matchtest` VALUES ('7', 'nofind 3'...
match/against doesnt find anything while like crashes the live server frequently ... live db has some 20000 rows (of 30 columns each); I´ve set up a test table with just for rows:
CREATE TABLE `matchtest` (
`id` varchar(32) NOT NULL default '',
`title` varchar(255) default NULL...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.