A domain characterizes the set of data that is valid in a particular column. When you assign a database column to a domain, you determine:
Defining domains enables you to make data meaningful to the end-user. It also allows you to standardize input checks on columns.
When developing your system, you will define a number of domain hierarchies, at least one for each RDBMS data type that your application needs. Each domain can have its own default value and its own help text. Even if you do specify them, however, you may overrule them at the column level.
When you define a domain, you can indicate that the domain has a superdomain. The inheritance of domain properties, and which properties a (sub)domain inherits from its superdomain is described in Help topic: "Inheritance of Domain Properties".
If you want the default value to be the current date, or the current date and time, you must specify one of the values:
A new date and time value is fetched from the server each time you refer to one of these functions. A different possibility is to use
In this case, the current date and time are fetched from the server only once within a transaction. If you refer to one of these functions again within the same transaction, an identical date and time value is returned.
If you want the default value to be the user name of the current user, specify:
You may overrule a domain default value at the column level. That is, when you specify a default value at column level, it overrules the default values of the domain on which it is based.