I recently posted about my corrupt table where no matter what options I tried REPAIR TABLE and myisamchk would "recover" the table but in the process reduce the size from 27,000 rows to just 1000. Not very useful.
In the end I managed to get almost all my data back by using a hex editor and a Perl script to scan the MYD file and parse it sufficiently that I could extract the main fields of interest from each record. (I ignored the MYI file completely so I've no idea what state that was in.) This process was significantly hindered by the complete lack of *any* documentation on the structure of MYD files, but fortunately I managed to persevere. I'm curious why myisamchk did such a poor job of it, though, given that virtually all the data still seemed to be recognisably there? -Rolf [Spam filter fodder: sql, query, ...] -- Rolf Howarth, Square Box Systems Ltd, Stratford-upon-Avon UK. --------------------------------------------------------------------- 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
