go to the c:\mysql\data\mysql directory and run,
c:\mysql\bin\myisamchk -e *.MYI > report.txt
and look through the report.txt file for errors.
Then run,
myisamchk -r <tablename>
on any table the report says has an error.
If that doesn't work, just reinstall MySQL.
You have to restart the server for the changes in the .ini
file to take affect.
Note that both the client and the server has it's own max_allowed_packet variable. If you want to handle big packets, you have to increase this variable both in the client and in the server. If both the client and...
To rename a table:
alter table product rename os-product;
To create a table based on your 'live' table:
create table product select * from yourlivedatabase.product;
[This assumes both databases are located on the same machine.]
Three host.{frm|MYD|MYI} files are installed in MySQL's data\mysql directory upon MySQL installation.
Did you accidently delete these files, or delete the data\mysql
directory, or delete the mysql database?
Just reinstall MySQL to reinstall these files.
You can get MySQL to not use InnoDB...
Version 4.0.1+ has full-text search capabilities that you allude to.
mysql> SELECT * FROM atable WHERE MATCH (field1,field2)
-> AGAINST ('+term1 +term2 -term3' IN BOOLEAN MODE);
This capability is only provided for the MyISAM table type.
There are no versions of MySQL, AFAIK, that...
There is a definitive WHERE clause: t.topic_moved_id =0
MySQL will key in on this clause because it is a constant.
The only problem is, I'm betting there are tons of 0's in this column,
so the index is being ignored (see below).
Have you done an 'ANALYZE TABLE nuke_bbposts, nuke_bbtopics'...
Glad to hear you worked it out.
Your key_buffer_size is too small for a machine that has 512MB.
Should be at least 100M instead of 16M.
This should be set in your my.ini/my.cnf file and the server restarted.
set-variable = key_buffer_size=100M
This setting will allow MySQL to store more...
Have you run 'EXPLAIN' on this SELECT query?
You may want to post the results of the EXPLAIN if it isn't clear.
You are creating two indexes on attach_id in the nuke_*_desc
table. Should delete the second index (KEY `attach_id`).
Have you tuned the server parameters? Can you change any of...
To create a temporary table that is automatically deleted
when the database connection is closed:
CREATE TEMPORARY TABLE tbl_name AS SELECT blah blah blah...
I've been upgrading from version 4.0.12 through 4.0.17
without any problems. I always overwrite the existing
version (except I rename the bin directory).
I think there would be problems,
however, if I upgraded to the alpha version 4.1.1, so
I haven't done that.
Yeah, you can install over a pre-existing installation
as long as MySQL is not running.
I would recommend, however, that you rename the bin directory
to something like 'bin_old' so the MySQL installation program
creates a completely new bin directory.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.