Posted on 09-18-2018 09:28 AM
About the InnoDB conversion and the tool to do it... We now have got the tool out from the Linux installer on a VM, and have run it on a dev instance. It asks for various values (pool size etc).
WEB-INF/xml/*
?Posted on 09-18-2018 09:38 AM
I though that if you didn't have
<DefaultStorageEngine>InnoDB</DefaultStorageEngine>
in your DataBase.xml file it'd default to MyISAM.
Posted on 09-18-2018 12:03 PM
If I can add one more question: Are there any special concerns or a particular order of operations we should follow when converting on a multi-context server with multiple JPSes/databases or is it not a concern since the engine is a per-table thing and not a global database thing?
Posted on 09-19-2018 12:14 AM
@Serge Where is this documented?
Posted on 09-19-2018 09:03 AM
@grahamrpugh I don't think it was. I had to add that line for my new production instance to create InnoDB tables by default, and when I converted my staging instance to InnoDB. This was a couple of years ago, when InnoDB was unsupported still.