WTSupported in traditional Synergy on Windows
WNSupported in Synergy .NET on Windows
USupported on UNIX
VSupported on OpenVMS
This environment variable was deprecated in Synergy/DE 9.3. We recommend setting the “Null allowed” Repository option to Yes or No for each field. See Preventing null updates and interpreting spaces, zeros, and null values.
The SODBC_NONULL environment variable setting determines how the “Null allowed” property is set in the system catalog for repository fields where the “Null allowed” Repository value is Default (rather than Yes or No).
One of the following values:
0 = Set all columns to “null allowed.”
1 = Set only date columns that aren’t part of the definition for the first key to “null allowed.” (This was the only supported behavior prior to Connectivity Series 9.3.)
2 = Set all columns to “null allowed” except those that are part of the first key definition.
3 = Set all columns to “null allowed” except those that are part of an access key.
4 = Set all columns to “null allowed” except integer, binary, Boolean, and non-date columns that are part of the first key definition.
By default, SODBC_NONULL is not set, which is the equivalent of setting it to 4. If you set this environment variable, set it before you generate the system catalog. Note the following:
- If a field generated from a struct field is part of a key definition in the structure used to create the struct field, dbcreate will consider it as part of the key when setting “null allowed.”
- For dbcreate to consider a field as part of a key, the field must be in a key definition in the repository (not an overlay in the same position as the key).
The environment where you run dbcreate.
In the environment on Windows,