-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/14 09:25, Danny Auble wrote:
> 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
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
-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 descr
That is exactly what it does. Evidently if innodb isn't there it just goes
along quietly without issue without innodb.
On July 3, 2014 4:38:24 PM MST, Christopher Samuel
wrote:
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>On 28/06/14 06:32, Kevin M. Hildebrand wrote:
>
>> I might have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/06/14 06:32, Kevin M. Hildebrand wrote:
> I might have missed it, but I didn't see any place in the SLURM
> install docs that mention that InnoDB is a requirement when using
> MySQL.
I'd suggest that for these cases it should use Engine=InnoDB
This has been added to the accounting web page. Thanks for the note. I
agree with the frustration of MySQL just chirping right along, no error
is even given when we specifically set the engine to InnoDB. Hopefully
this has only bitten a couple of people, and hopefully the documentation
updat
