Fulltext boolean search v.2.2 for vB

Hello all!

Moving here from beta forum
https://vborg.vbsupport.ru/showthread.php?t=62218

This hack makes nearly same for vB3 as
[vB 2.2.x] - Mysql 4 Search hack
https://vborg.vbsupport.ru/showthread.php?t=51716
for vB2

You will need MySQL server v4.0.1 or better (but sometimes it may work on 3.23.xx). After installing you will be able to search with empty native vB index (word and postindex tables) and using modifiers.
Allowed modifiers + are ,-, * and "
All modifiers except * should be used only once for one word (in the beginning and without space).
* it should be used at the end of a word.
For example:
windows unix -> will find messages containing at least one these words.
+windows +unix -> will find messages with both this words.
windows* -> will find "windows", "windowss", "windowssauce" or "windowst".
*indows will NOT find "windows"
"some words" -> will find "some words of wisdom", but will not find "some extra words".
Search phrase length limitations replaced with results number limitation.
Value of old "Search Index Maximum Word Length" used to limit number of posts in the result returned by fulltext search (control panel/Message Searching Options)
Supposed that it must run faster then native vB search

History:
v.2.2 [5 Apr 2004]
- search words relevance (when sort by relevance) added at last
but little different then native vB (it may not work when searching with * modifiers)
- attempt to fix incompatibility with other hacks
=to upgrade replace code block #5 in search.php with latest one

v.2.1 [4 Apr 2004]
- Excluding from search forums with "Index New Posts in Search Engine" option set to "No"

v.2.0 [30 Mar 2004]
-"Similar Threads" now must start working (to move from 1.x to 2 just change one more script - functions_search.php)

v.1.9 [29 Mar 2004]
-checking if $query string is not empty before running fill text sql

v.1.8 [20 Mar 2004]
- line numbers and higlight code changed for VB3 Gold
- more tests and error explanations

v.1.7 [9 Mar 2004]
- MySQL error for administrators bug fixed
checking is $not_forumid string exixts before adding it to query

v.1.6 [9 Mar 2004]
- national letters bug fixed
preg_replace("~[^\w\"\-+\* ]~i", "", $query);
was replaced by
preg_replace("~[^\w\xC0-\xFF\"\-+\* ]~i", "", $query);

v.1.5 [8 Mar 2004]
- TABLE_PREFIX bug fixed
- slightly optimised SQL requests

v.1.4 [8 Mar 2004]
- delete_post_index function turned off
- more tests and error explanations

v.1.3 [7 Mar 2004]
- less code because of using native vB $postQueryLogic and $threadQueryLogic conditions
- more tests and error explanations

v.1.2 [7 Mar 2004]
- boolean mode can be turned off in AdminCP ("Allow Search Wild Cards" setting)
- "titles only" search fixed
- limiting number of matches retunned by fulltext search AFTER applying search conditions

v.1.1 [7 Mar 2004]
- HighLight support added

Originally Posted by msimplay

Someone has already used the same hack with vb3.06 its installed

yeah, i know, but the hack require some changes to be following the 3.0.6 structure of codes... i know it's possible to install it...

[msimplay]

Originally Posted by nexialys

yeah, i know, but the hack require some changes to befollowing the 3.0.6 structure of codes... i know it's possible toinstall it...

what exactly happens when u try to use the installer ?

hum.. little request here...

vB 3.5 will have the FullText integration complete, is there a beta tester here that knows if THIS hack is the same as the one they will introduce in 3.5 or if it's a complete different story ?!

[kmike]

Fulltext search is available in official vB release ever since version 3.0.2. Though it isn't supported - you have to know where to look to enable it.
Conceptually this hack should be very similar to vB's own implementation. Details will differ of course.
The point is, you can already have look at the official fulltext search code, and compare it to this hack.

... hum... you did not follow the topic, why do you answer this ?!...
and also, look at who you're talking to, you'll spare some words... (yes i'm the guy in perpetual bad mood)

[JohnWoo]

And I can say only sorry I have never seen vb3 other then vb3.0.0 Gold and can't say something exactly...

[David Bott]

Hello John...(Running 3.0.6 (this security updates applied.)

I have a question if I may. I see your full text search requires two different indexes in the post table. One is TITLE and the other is PAGETEXT (keynames). Looking at the structure for the POST table I see these two indexes with pagetext having a 1 after it.

Now looking at how Vb asked for it to be done, they want you to run...

ALTER TABLE post ADD FULLTEXT INDEX (title,pagetext);
ALTER TABLE thread ADD FULLTEXT INDEX (title);

This results, as you know, in a single new index in POST for TITLE that has both TITLE and PAGETEXT in one keyname. (title). Then they wanted another full text search index for the THREAD table for TITLE.

My questions, because I really do not know...

1) What is the difference having two keynames in the POST table, like yours, and only having one (theirs)? What does help with?

2) Does it matter, or will it help, with your code to have the full text search index in the THREAD table like they requested? (I made it just in case.)

I have your code now running on TiVo Community Forum and I am looking to run it on AVS Forum (Even though it is from last year, I hope the code is still ok with the current version Iam running). I am looking for solutions for we are getting killed with the searches more so on AVS Forum. (We went to VB3 last Sunday.)

Thank you for your time.

(Note...I noticed in the VB3 search.php it really needs help. Espically when you have it limite the return. It still searches and returns ALL HITS and then purnes it down to the limit number. Thus the return is still very large. I think your code actually does it correct by stopping when it reached the limit.)

Update...I just installed it on AVS Forum. It took my MySQL load from 1.4 (or more) to currently .38 with 2000 users on-line.

Just need to know why.

[David Bott]

Hello Again...

Sad to see no answer to the above. So far the code seems to do very well. But still would love to know why it seems to have a lesswof an impact on MySQL vs what VB3 used.

[kmike]

Originally Posted by David Bott

Now looking at how Vb asked for it to be done, they want you to run...

ALTER TABLE post ADD FULLTEXT INDEX (title,pagetext);
ALTER TABLE thread ADD FULLTEXT INDEX (title);
...
1) What is the difference having two keynames in the POST table, like yours, and only having one (theirs)? What does help with?

Two indexes are required to search both title AND post text in default search mode.

[David Bott]

Hello...

Yes, I do see that and have it that way and all is well.

But th questionis as to why. Just wondering what the difference is and why do it that way vs the way VB asked for it to be done. It is more affective? Do I still need the "ALTER TABLE thread ADD FULLTEXT INDEX (title);" as they request?

I guess I am seeking why this hack works so much better than the VB3 version of the Full Text Search.

Thank you.