Hi all. I'm new to MySQL, so please forgive me if this issue is
already well-known.
I'm running MySQL server 3.23.28-gamma-debug on WinME. Yes, I know,
that version is almost 2 years old (and the OS is lousy, don't bother
to tell me). It came on a CD that came with a book, so I installed it
for convenience just to casually play around instead of waiting for a
fresh version to download.
I'm having a problem that's shaking my faith in MySQL, though, so I'd
like to see if I can get an answer to it before I just go and upgrade
the server version.
I made a table where one field is TEXT type. I put a few records into
the table (never more than 3 records!), then ran a check on it, and it
was fine. Ran a repair, that was fine. Ran an "extended" repair, and
got a few "info" messages such as "Found block that points outside data
file at 72". In some cases, the extended repair went on to work
("status"/"OK" below those "info" lines), but in other cases it showed
"error" messages and it couldn't do the repair! Also, sometimes other
errors would be produced upon then attempting to drop the table (the
code "13" comes to mind), and only some of the table's files would be
deleted and I'd have to delete the others manually after shutting down
mysqld.
I then simplified the table greatly, and still got the "block that
points outside" "info" messages on an extended-repair. Here's a very
simple example using a simplified table:
CREATE TABLE clients (
client_id int(10) unsigned NOT NULL auto_increment,
zip mediumint(5) unsigned zerofill DEFAULT '00000' NOT NULL,
description text,
PRIMARY KEY (client_id),
KEY IDX_zip (zip)
);
INSERT INTO clients VALUES (null,12345,'This is the description for the
first client');
INSERT INTO clients VALUES (null,67890,'This is the description for the
second client');
I run that, then do an extended-mode repair, and I get those "Found
block that points outside data file at..." messages. The original
version of the table, that has more fields, would sometimes also cause
the more serious problems noted above (can't repair, errors in dropping
table), and sometimes not.
This is quite recreateable and repeatable; I've created / populated /
extended-repaired / dropped both simple and more complex versions of
the table over and over, and I always get at least the "info" messages
above. I've never put more than 3 records in these tables, either!
Any ideas? This is quite disturbing. It never seemed to affect the
ability to read the table's contents ("SELECT * FROM clients" always
worked fine), and changing the TEXT field to VARCHAR(255) solves the
problem beautifully, but the fact that a supported column type (TEXT)
can produce weird extended-repair messages and sometimes even corrupt
the table (at least enough to prevent repair/drop) with only THREE
records present is quite unsettling. I want to use MySQL for a
production application and this has me nervous. I need excellent
stability/reliablity.
Thanks guys! If you could, please Cc: me on any replies because I'm
not a subscriber to the list. Thanks!
__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
