From: Reindl Harald
Date: April 29 2012 1:01pm
Subject: Re: engine is now innoDB instead of MyISAM.
List-Archive: http://lists.mysql.com/mysql/227265
Message-Id: <4F9D3BB8.9030300@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig94B576A0D9EDFCB5FE160EE4"

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



Am 29.04.2012 14:50, schrieb Brown:
> is a complain I received from one of my developer that after following =
our MySQL=20
> Cluster migration, tables are now defaulting to innodb (how can he tell=
)=20

as already said:

the builtin default has changed an you have to configure MyISAM
as default yourself with "default-storage-engine =3D myisam"

and yes, InnoDB can be a big problem if your application is only
tested against MyISAM because it works completly different inside



--------------enig94B576A0D9EDFCB5FE160EE4
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://enigmail.mozdev.org/

iEYEARECAAYFAk+dO8YACgkQhmBjz394AnloNgCfRrdMF7hNhk5ID4uQTlvxcFaN
3OEAoJPPg7xESVHen0WYGV1H1OuFwwY+
=RIi2
-----END PGP SIGNATURE-----

--------------enig94B576A0D9EDFCB5FE160EE4--