SQL:2011 spec, 10.8, uses [ NOT ] ENFORCED for column constraint characteristics.
I think Oracle invented DISABLE and NORELY and maybe others have copied it over time.
A quick check I see DB2 uses the [ NOT ] ENFORCED. Teradata uses something else entirely.
Personally I think there are advantages to adopting the standard approach.
There is no standard approach for hinting the optimizer so we're on our own there.
- relates to
HIVE-16575 Support for 'UNIQUE' and 'NOT NULL' constraints
- links to