Re: REPAIR/CHECK/BACKUP/RESTORE TABLE handling of compressed tables leads to data loss.

Giuseppe Maxia <[email protected]>
Newsgroups gmane.comp.db.mysql.bugs
Organization StarData
Message-ID <1085588688.2658.7.camel@LTGmax>
Il mer, 2004-05-26 alle 17:59, Sinisa Milivojevic ha scritto:
Hi Sinisa,
Thanks for your quick answer. I have just a couple of points.


> Thanks for writting to us.
> 
> Short answers to your questions.
> 
> 1) Any write operation on compressed table is not permitted and will
>    result in damaged table. This is documented in a manual.
> 

True. 
REPAIR TABLE actually recognizes that the table is read-only, and it
still attempts to write. 
This, IMO, should be treated as a bug just like the following case.

> 2) Not checking for compressed table, like with BACKUP / RESTORE is a
>    bug. We shall enteri it into our bugs system
> 

Thanks

> 3) myisamchk can not operate at all without index file. Documented
>    behaviour as per our manual. 

Therefore, a compressed table with a damaged or missing index cannot be
recovered. 
Is that correct?

Thanks

Best regards

Giuseppe Maxia


-- 
Giuseppe Maxia
CTO
http://www.StarData.it
       __              __     __
  ___ / /____ ________/ /__ _/ /____ _
 (_-</ __/ _ `/ __/ _  / _ `/ __/ _ `/
/___/\__/\_,_/_/  \_,_/\_,_/\__/\_,_/
       Database is our business



-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.