Thanks for the tip Chris, I hadn't noticed it before. It is committed
in 14.11 commit da24acfc359ef9e28866c82fb9f9e9880235fcaa
The DBD will now print a nice error about InnoDB not existing and halt
if it isn't available.
Danny
On 07/03/2014 08:23 PM, Christopher Samuel wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/07/14 10:07, Danny Auble wrote:
That is exactly what it does. Evidently if innodb isn't there it
just goes along quietly without issue without innodb.
Wow, I'd assumed it would report an error in that case, but apparently
not. This describes what happens and how to get it to fail instead.
http://dev.mysql.com/doc/refman/5.6/en/storage-engine-setting.html
# By default, a warning is generated whenever CREATE TABLE or
# ALTER TABLE cannot use the default storage engine. To prevent
# confusing, unintended behavior if the desired engine is
# unavailable, enable the NO_ENGINE_SUBSTITUTION SQL mode. If
# the desired engine is unavailable, this setting produces an
# error instead of a warning, and the table is not created or
# altered. See Section 5.1.7, “Server SQL Modes”.
cheers!
Chris
- --
Christopher Samuel Senior Systems Administrator
VLSCI - Victorian Life Sciences Computation Initiative
Email: [email protected] Phone: +61 (0)3 903 55545
http://www.vlsci.org.au/ http://twitter.com/vlsci
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlO2HdIACgkQO2KABBYQAh+x+gCfcA8tzRbYvK3X+kZz3DSQgohS
i6AAn1I72z5GRUCEnN+qncD3Dgxz3269
=I5Bo
-----END PGP SIGNATURE-----
