At 12:40 -0600 3/24/04, Daniel Gaddis wrote:
> From: Victor Pendleton [mailto:[EMAIL PROTECTED]
This error should be logged. Do you have a file called <hostname>.err
in your
directory?
Yes I have a file called <hostname>.err and that error is not in it.
From: Paul DuBois [mailto:[EMAIL PROTECTED]
The error log is for messages pertaining to problems with the
operational
state of the server. Normally there's not much in it at all.
The error you show above is a problem with a query sent by a client.
That type of error message is sent to the client, not logged.
the query (see below) seems to be okay. the problem doesn't seem to be
with the query, but with the table.
UPDATE referenceEntries SET heading =
'Delete', body = '',
keywords = '' ,
dateVerified = NULL WHERE entryID
= 168
the error (see below) seems to be the first indication of a corrupt
table. So wouldn't that be a server issue and be appropriate to log into
the mysql error log?
I suppose you could consider it such, but on the other hand, it's not the
sort of error that prevents the server from running or processing other
queries. In any case, logging it to the error log isn't going to help
the client know what is going on and that it should attempt to run a table
repair operation. Perhaps what you are suggesting is that the message
should go to both places?
Incorrect key file for table: 'referenceEntries'. Try to repair
it
The manual makes a reference to this error in Section 14.1.3.1 Corrupted
MyISAM Tables...
Typical symptoms for a corrupt table is:
You get the error Incorrect key file for table: '...'. Try to
repair it while selecting data from the table.
Thanks,
Daniel
--
Paul DuBois, MySQL Documentation Team
Madison, Wisconsin, USA
MySQL AB, www.mysql.com
MySQL Users Conference: April 14-16, 2004
http://www.mysql.com/uc2004/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
