I'm not talking about non-committed rows lost (nothing can be done about those..) I'm talking about broken indexes causing rows which are already on disk to become orphaned and disappear when you do a repair.
Granted MySQL has come quite a ways since my bad experience. But it's still something to think about. By definition silent losing of rows is.. all but undetectable. Maybe use InnoDB table type? i believe since InnoDB has the standard "two log files" used by "real" databases since, oh.. 1986.. it should be more resilient to these sorts of things. On 2/11/07, Roberto Verzola <[EMAIL PROTECTED]> wrote:
On Sunday 11 February 2007 1:11 pm, Orlando Andico wrote: > The more sinister part of this is, the repair method sometimes loses rows. > :P But then you'll never know. But it happened to me before, with rather > ill results. Yes, I can imagine that can happen, if power is lost while files are open. A reliable UPS would be one solution. Or are you driving at an even better solution? |-)
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
