slowandeasy has in theory practical soltion without changing the board program but would be impossible to get posters to studder in their posts so can be found. But very creative solution.
Better solution is when the board can go to full-text searching instead of current indexing of words. Full-text searching is now supported in latest version of My SQL which is the database engine that runs the VBulletin board used here (and very good except for small word search problem):
I have researched the short word problem by looking at the discussions on the vBulletin board.
It seems Fred can set the minimum value but If you set a smaller value (3), you could search for posts containing "Ivy" but the data base would grow massively in size to contain all 3 letter words users post such as any, and, but and zillions of other common words
The search in vBulletin 3 (now out but in Beta) is being reworked a little to make it more logical but it won't be able to over-ride the minimum characters that are set by the administrator. That would take full-text search which won't be usable until MySQL 4.0 comes out of beta which is slated for the end of the year (2002).
Using full-text search reliably in vBulletin is on the list of things to add but most likely won't be until after vBulletin3.0 (now out in Beta).
As of May 2003 My SQL is up to Version 4 beta - As of Version 3.23.23, MySQL has support for full-text indexing and searching. Full-text indexes in MySQL are an index of type FULLTEXT. FULLTEXT indexes are used with MyISAM tables and can be created from CHAR, VARCHAR, or TEXT columns at CREATE TABLE time or added later with ALTER TABLE or CREATE INDEX. For large datasets, it will be much faster to load your data into a table that has no FULLTEXT index, then create the index with ALTER TABLE (or CREATE INDEX). Loading data into a table that already has a FULLTEXT index will be slower. Full-text searching is performed with the MATCH() function.
posts about db size:
1/03 - I've only 75000 posts in the database but 3.577.005 entries in the searchindex table ( size of 87.8 MB ).
Is this table to big? Can I reduce this size? When gets mysql problems?
Replies: That sounds like a typical size. The only way to reduce this is to increase the minimum word length and decrease the maximum word length of the words that get indexed. Of course this will reduce the effectiveness of your search option.
Check this thread out. It helped me reduce my searchindex from 220 megs to 100 megs. http://www.vbulletin.com/forum/show...?threadid=39587
How about support for full text searching?
Full text searching is already available in MySQL version 3. Version 4 enhances it by adding boolean capability. Version 4 (4.0.8) is now in gamma and will probably be final before vB 3 is released.
I've actually been using version 4 and full text search since 4.0.1. The later versions have proven to more stable for me than version 3 ever was.
Support for this feature is easy to add (I even managed to hack it in with Ed's help). It won't affect performance for those who want to use the standard searchindex method, vB will be ready for the future and everyone will be happy... then in vB 4 we can have foreign constraints and start thinking about stored procedures in preperation for MySQL 5.
Another says: A quick glance at the the first line of section 6.8 in the MySQL manual reads:
As of Version 3.23.23, MySQL has support for full-text indexing and searching.
The only thing missing from version 3 is the boolean search. Relevency seaching is fully supported.
Gossamer Threads have the option of fulltext indexing plus their own internal method with weighting. If they can have it, why can't we?
Reply by "VBulletin team member": Hmmm...all I can do is ask the Developers to comment on this.
Dave says, I know nothing about MySQL and how you integrate Vboard with it with the different indexing options. Perhaps this may be helpful to Fred or other "geeks" who may be data base experts. It is clear the word limit is a major issue with VBulletin boards and is trying to be addressed. I have not read all the manuals for the latest version and by using search's on their support board I can't find any more on point posts.