Hi, I've reported this problem several months ago. One of the problems is the definition of the intag column. It should be int(11) but the optimize script recreates it as a tinyint(4), which brakes the relevancy information.
How it should be: CREATE TABLE ndict2 ( url_id int(11) DEFAULT '0' NOT NULL, word_id int(11) DEFAULT '0' NOT NULL, intag int(11) DEFAULT '0' NOT NULL, KEY url_id2 (url_id), KEY word_id2 (word_id) ); What the optimize script does: CREATE TABLE ndict$TABLE ( url_id int(11) DEFAULT '0' NOT NULL, word_id int(11) DEFAULT '0' NOT NULL, intag tinyint(4) DEFAULT '0' NOT NULL, KEY url_id$TABLE (url_id), KEY word_id$TABLE (word_id) ) I find it much safer to use myisamchk with --sort-records. The result is the same: the records are sorted. An additional advantage is that people can keep searching while you are optimizing the tables. You just can't have the indexer running at the same time. If you want to use the script anyway and you have a password, then you must modify the script. Change every line that uses the mysql program etc. and include your password with -p. regards, kristof Alexander Barkov writes: > Author: Alexander Barkov > Email: [EMAIL PROTECTED] > Message: >> Addition to that it destroyed my database like it warned before running it :( > > What exactly happened? > > This script is contribuited program, we don't > support it. But it's interesting anyway, what > exactly was distroyed? Probably the reason is > not script. > > Reply: <http://www.mnogosearch.org/board/message.php?id=4219> > > ___________________________________________ > If you want to unsubscribe send "unsubscribe general" > to [EMAIL PROTECTED] > ___________________________________________ If you want to unsubscribe send "unsubscribe general" to [EMAIL PROTECTED]
