From: Gleb Paharenko (gleb.paharenkoensita.net)
Date: Tue Jul 05 2005 - 08:48:00 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello.

Yes, it works only for MyISAM. You've began a new thread, and
haven't specified that this one is related to the previous. So
I've decided they were independent. Possibly you could obtain
schema information using different levels of innodb_force_recovery.
See:
  http://dev.mysql.com/doc/mysql/en/forcing-recovery.html

Jason Pyeron <jpyeronpdinc.us> wrote:
> On Tue, 5 Jul 2005, Gleb Paharenko wrote:
>
>> Hello.
>>
>> As of MySQL 4.0.2 after REPAIR ... USE_FRM you should be able to get information
>> about table with SHOW CREATE TABLE, however some information could be lost.
>> See:
>> http://dev.mysql.com/doc/mysql/en/repair-table.html
>>
>
> but doesn't that only work with MyISAM tables?
>
> from the web page:
>
> REPAIR TABLE repairs a possibly corrupted table. By default, it has the
> same effect as myisamchk --recover tbl_name. REPAIR TABLE works only on
> MyISAM tables.
>
> mysql> repair table files USE_FRM;
> +-----------------+--------+----------+-----------------------------------------+
> | Table | Op | Msg_type | Msg_text
> |
> +-----------------+--------+----------+-----------------------------------------+
> | crisfield.files | repair | error | Can't open file: 'files.ibd' (errno: 1) |
> +-----------------+--------+----------+-----------------------------------------+
>
> files.ibd does not exist on the system.
>

--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __ ___ ___ ____ __
  / |/ /_ __/ __/ __ \/ / Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__ Gleb.Paharenkoensita.net
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
       <___/ www.mysql.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]