Admin Setting functions
| > Module written by Matt Mecham
| > Date started: 20th March 2002
|
| > Module Version Number: 1.0.0
+--------------------------------------------------------------------------
*/
if ( ! defined( 'IN_ACP' ) )
{
print "
Unable to automatically create the FULLTEXT indexes
You have too many posts for an automatic FULLTEXT index creation. It is more than likely that PHP will
time out before the indexes are complete which could cause some index corruption.
Creating FULLTEXT indexes is a relatively slow process but it's one that's worth doing as it will save you
a lot of time and CPU power when your members search.
On average, a normal webserver is capable of indexing about 80,000 posts an hour but it is a relatively intense process. If you
are using MySQL 4.0.12+ then this time is reduced substaintially.
How to manually create the indexes
If you have shell (SSH / Telnet) access to mysql, the process is very straightforward. If you do not have access to shell, then you will
have to contact your webhost and ask them to do this for you.
Step 1: Initiate mysql
In shell type:
mysql -u{your_sql_user_name} -p{your_sql_password}
Your MySQL username and password can be found in your conf_global.php file
Step 2: Select your database
In mysql type:
use {your_database_name_here};
Make sure you use a trailing semi-colon. Your MySQL database name can be found in conf_global.php
Step 3: Indexing the topics table
In mysql type:
\g alter table ibf_topics add fulltext(title);
If you are not using 'ibf_' as your table extension, adjust that query to suit. This query can take a while
depending on the number of topics you have.
Step 4: Indexing the posts table
In mysql type:
\g alter table ibf_posts add fulltext(post);
If you are not using 'ibf_' as your table extension, adjust that query to suit. This query can take a while
depending on the number of posts you have. On average MySQL can index 80,000 posts an hour. If you are using MySQL 4, the time is greatly reduced.
";
}
}
?>