There is a method of always entering mandatory check and a method of keeping warning display.
The item name of the item for which the mandatory check is specified is displayed in red. If you move the cursor with no input, it will be checked in real time as shown in Figure 1.
"Input check - required" is set to "O" in the detailed item setting dialog of the model item.
Items for which "Warning" is set are also displayed in red letters. If you do not enter it, a warning will be displayed, but you can register again by clicking the "save" button again.(FIGS. 3 and 4)
"Input check - required" is set to "warning" in the detailed definition of the model item.
When the item is required, the following initial value is automatically set.
|Item type||initial value|
|Integer/1 byte integer/2 byte integer/4 byte integer/8 byte integer||0|
|4 byte floating point/8 byte floating point number||0.0|
When this setting is made, a NOT NULL constraint is added to the relevant item of the table definition.That is, the table schema is changed.
Be careful when reusing an existing table schema.
Specifically, if a mandatory item has a NULL value, that data will not be hit by a search from Wagby.[More ...]
Suppose you define a submodel and do not perform mandatory checks on the relevant items on the submodel side. (In other words, we assume a situation that mandatory checks are set for items on the main model side, but mandatory checks are not set for items on the submodel side.)
In this case, the main model performs the mandatory check, and the submodel does not perform mandatory check.
With this setting, the NOT NULL constraint is not set in the table definition.
"Use as a primary keyIf the setting is checked, mandatory check is automatically enabled and can not be changed.