From: Reindl Harald
Date: October 19 2012 8:59am
Subject: Re: Table crashed error
List-Archive: http://lists.mysql.com/mysql/228462
Message-Id: <50811654.7050408@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigB3A8BCAE9AA324F6833A3B89"

--------------enigB3A8BCAE9AA324F6833A3B89
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Am 19.10.2012 08:42, schrieb Dehua Yang:
> MyISAM storage tables  also have this kind of problem.
>=20
> I have try serval solutions for this problem , but can't work  very wel=
l.
>=20
> If your application isn't very import , you can let your application au=
to
> repair this problem.
> Just like this :
> When your application catch this error information , run check table xx=
x.

oh no, do not write useless code in the application
for things the server is able to do

my.cnf:
myisam-recover =3D "FORCE"


--------------enigB3A8BCAE9AA324F6833A3B89
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCBFlQACgkQhmBjz394AnnOjACgh4GJoHqnSSQta2havxF1P/8g
ZTYAnj4c8D0tsLgNJQdNnzt91akKa8XK
=B+8e
-----END PGP SIGNATURE-----

--------------enigB3A8BCAE9AA324F6833A3B89--