Any way to turn off certain warning messages during verification?

[Brian Sims]

This has been bugging me for a couple of months, but as long as I'm asking questions today, is there anyway to turn off certain error messages during database, validation (mysql), validate all? In my database design, I'm getting 180 warnings, but the database works just fine.

The first of two main types of warnings I'm getting are in the table validation routines and are as follows:

15:48:12 | Undefined type for column 'Material' in table 'SAPMaterialMaster'.
15:48:12 | Undefined type for column 'SAPMaterialType' in table 'SAPMaterialMaster'.
15:48:12 | Undefined type for column 'OldMaterialNumber' in table 'SAPMaterialMaster'.
15:48:12 | Undefined type for column 'BaseUnitOfMeasure' in table 'SAPMaterialMaster'.
15:48:12 | Undefined type for column 'Material' in table 'SAPMaterialPlant'.
15:48:12 | Undefined type for column 'Plant' in table 'SAPMaterialPlant'.
15:48:12 | Undefined type for column 'ProfitCenter' in table 'SAPMaterialPlant'.
15:48:12 | Undefined type for column 'MaterialPlantSAP_Material' in table 'SAPMaterialPlant'.
15:48:12 | Undefined type for column 'MaterialPlantSAP_Plant' in table 'SAPMaterialPlant'.
15:48:12 | Undefined type for column 'MaterialType' in table 'MaterialType'.

All these columns are defined as a 'user type' and are typically varchar types although I have a few like decimal(10,0) sprinkled about. Once the user type was defined in the 'catalog, layers, user types' pane, they were drug onto the column definition in the table columns tab. The exported create sql works just fine. I get so many of these that they would make a warning I should be concerned about hard to find.

The second class of warnings I would like to turn off are enumeration types and invalid defaults - although it could be something I'm doing. For example:

15:48:12 | Invalid default value ''N'' for column `UOM_Conversion`.`ValidForAll`: .
15:48:12 | Invalid default value ''N'' for column `Routing`.`IssueRequiredOnStart`: .
15:48:12 | Invalid default value ''N'' for column `Routing`.`IssueRequiredOnFinish`: .
15:48:12 | Invalid default value ''N'' for column `PlantOperations`.`Reportable`: .

The generated sql for the above warnings are:

CREATE TABLE IF NOT EXISTS `NNerp`.`UOM_Conversion` (
...
`ValidForAll` ENUM('N','Y') NULL DEFAULT 'N' ,
...


CREATE TABLE IF NOT EXISTS `NNerp`.`Routing` (
...
`IssueRequiredOnStart` ENUM('N','Y') NULL DEFAULT 'N' ,
...
`EndConfirmation` ENUM('N','Y') NULL ,
`IssueRequiredOnFinish` ENUM('N','Y') NULL DEFAULT 'N' ,
...

CREATE TABLE IF NOT EXISTS `NNerp`.`PlantOperations` (
...
`Reportable` ENUM('N','Y') NULL DEFAULT 'N' ,
...

On these fields in the table columns tab, I have ENUM('N','Y') in the datatype column, Not Null unchecked, AI not checked and 'N' in the default column. Is that the correct way to enter those columns or should I be checking the NN box?