Hi Abraham :)
I think the problem is that your expecting a precise answer to an imprecise
situation. We're talking about a large number of factors: connection speed, CPU
load and speed, current hard disk activity and controller speed, etc, etc.
There is no way to exactly predict the outcome of a catastrophic system failure
because the current state of the system (in the broad sense) cannot be known at
the time of the failure. This would be true for any RDBMS, even with
transactions or a journaling file system. Now, with a transactional DB it _may_
be easier to recover the previous state of the DB, but the situation your
presenting (the DB simply disappears arbitrarily) provides to many variables to
consider all the eventual outcomes :) isamchk may be equally efffective in
restoring the DB to a consistent state.
Hood
Abraham vd Merwe <abz@stripped> on 03/30/2000 08:39:14 AM
To: sinisa@stripped
cc: mysql@stripped (bcc: Hood Gardner/SpeedlineAmericas/Cookson)
Subject: Re: MySQL sessions
Hi!
> Yes, you are right, but since MySQL is so fast, probability that
> something like that occurs is very low, particularly if schema and
> queries are well optimised.
Very reassuring, but I'm a programmer, not a gambler (:
Regards
Abraham
--
---------------------------------------------------------------------
Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
posting. To request this thread, e-mail mysql-thread32718@stripped
To unsubscribe, send a message to:
<mysql-unsubscribe-hgardner=speedlinetech.com@stripped>
