In the data builder, if I have mandatory numeric column where I specify a minimum and maximum value, for example 1 and 10, I get an error when I save it if I don’t provide a default value. This is not the behaviour I would like.
I would like to put in a constraint for anyone updating the table that values for that column must be between 1-10. If they don’t supply the value I want the update to be rejected with an error. A default value in this case would be misleading and harmful.
Is it not possible to have a mandatory numeric field with a non-zero minimum and no default value?
If I select Mandatory, and the minimum is non-zero, I do have to provide a default. This is the problem. I want a mandatory field without a default. This is so that a user of the API will get an error if they don’t supply an intentional value for the field.