Unnecessary validation of 'mysql' schema during the js-upgrade-samedb script

Issue Description

In some circumstances users might not like the validation of 'mysql' schema which occurs during the js-upgrade-samedb script, and this can be configured to not occur. Often the upgrade process will need to drop and recreate the db entirely due to large changes (removal of tables, or major table changes, etc). So this is why the upgrade process is doing this validation of 'mysql' schema js-upgrade-samedb script. In some particular version combinations, 'samedb' isn't dropping or creating, rather it is just updating, therefore it does not need access to the 'mysql' schema.

If the validation is problematic for you because it is failing due to permissions issues (for example if changed after initial install) you can change the scripts.

Resolution

If the validation of 'mysql' schema, aka admin, is problematic for you, edit <install>buildomaticvalidation.xml and comment out the line below

From:

validateDB systemName="admin" phase="test" failOnDBNotExists="true" />

To:

<!--   <validateDB systemName="admin" phase="test" failOnDBNotExists="true" />   -->

Ref. Case 01540154