Re: [PHP] Full-text searches sucks?

2005-03-22 Thread Ryan A
Hey, I dont want to do that as its only mysql 4.1+ compatable, IN BOOLEAN MODE was added in version 4.0.1 not 4.1, for what it's worth. Oops, thats what i meant. The problem is a LOT of hosts are still on 3.23.xx so I dont want to do the BOOLEAN MODE thing. -Ryan On 3/21/2005 8:51:07

[PHP] Full-text searches sucks?

2005-03-21 Thread Ryan A
Hey all, I just put in a search function for a site using mySql full text, i am running it on my local server for now. I am running it on two fields: ad_sub and ad_text The results i getting are really quite bad, this is how i am testing it out: 1. I wrote an insert statement and looped it 700

Re: [PHP] Full-text searches sucks?

2005-03-21 Thread Larry E . Ullman
which means because I i getting a match for well over 50% of the records...its disregarding it. Yes, this is exactly the problem. Now i am in two minds if i should use this or go back to the same old dirty way...of exploding the search and using LIKE '%%' for each word FULLTEXT searches are

Re: [PHP] Full-text searches sucks?

2005-03-21 Thread Ryan A
Hey! Thanks for replying. FULLTEXT searches are great; it's your testing of them that is poor. Kind of true, but I would have still been happy if it had found some records rather than 0 results. Also, FULLTEXT searches are improved as the number of __different__ records increase. Yep, I

Re: [PHP] Full-text searches sucks?

2005-03-21 Thread Larry E . Ullman
Thanks for replying. You're quite welcome. If you want to see some results, regardless of the 50% threshold, use the IN BOOLEAN MODE feature. Keep in mind, though, that in your case any search will return either 0 or 700 results. I dont want to do that as its only mysql 4.1+ compatable, IN BOOLEAN