For an Enterprise GeoDatabase, I'd like to restrict the values of a feature class' field to a range of values. Essentially, I want validation at the database level, so that regardless of how the data is being inserted, the constraints are persisted (e.g. ArcGIS for Server feature service, ArcPy, ArcMap, ArcObjects, etc.). I tested domains, however I noticed that from the feature server service endpoint I can insert a value outside of my specified range.
For example, if I specify a range to 0 to 1, I can set the field to 6 from the service endpoint and it will be inserted into the GeoDatabase successfully.
I think database triggers or possibly creating a server object extension may be the only option.