Commit 16041ad1 authored by paul@teton.kitebird.com's avatar paul@teton.kitebird.com

Merge paul@work.mysql.com:/home/bk/mysql-4.0

into teton.kitebird.com:/home/paul/mysql-4.0
parents 9f0ac6db 4bf55194
...@@ -17724,9 +17724,9 @@ by row instead of creating one index at a time with sorting; This may be ...@@ -17724,9 +17724,9 @@ by row instead of creating one index at a time with sorting; This may be
better than sorting on fixed-length keys if you have long @code{char()} better than sorting on fixed-length keys if you have long @code{char()}
keys that compress very good. keys that compress very good.
As of MySQL 4.0.2 there is @code{USE_FRM} mode for @code{REPAIR}. As of @code{MySQL} 4.0.2 there is a @code{USE_FRM} mode for @code{REPAIR}.
Use it if @file{.MYI} file is missing or its header is corrupted. Use it if the @file{.MYI} file is missing or if its header is corrupted.
In this mode MySQL will recreate the table, using information from In this mode MySQL will recreate the table, using information from the
@file{.frm} file. This kind of repair cannot be done with @code{myisamchk}. @file{.frm} file. This kind of repair cannot be done with @code{myisamchk}.
@node Table maintenance, Maintenance regimen, REPAIR TABLE, Disaster Prevention @node Table maintenance, Maintenance regimen, REPAIR TABLE, Disaster Prevention
...@@ -18391,8 +18391,8 @@ a copy in case something goes wrong.) ...@@ -18391,8 +18391,8 @@ a copy in case something goes wrong.)
Go back to Stage 2. @code{myisamchk -r -q} should work now. (This shouldn't Go back to Stage 2. @code{myisamchk -r -q} should work now. (This shouldn't
be an endless loop.) be an endless loop.)
As of MySQL 4.0.2 you can also use @code{REPAIR ... USE_FRM} As of @code{MySQL} 4.0.2 you can also use @code{REPAIR ... USE_FRM}
that does the whole procedure automatically. which performs the whole procedure automatically.
@noindent @noindent
@strong{Stage 4: Very difficult repair} @strong{Stage 4: Very difficult repair}
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment