The v60SQLNullableBehavior build
descriptor option affects how EGL behaves when a null value is assigned
to a variable.
Starting with version 7, EGL throws a SQL Exception in the following
circumstances:
- An SQL query returns a null value.
- You assign the value to a variable for which the isSQLNullable property
is not set to YES (that is, set to NO, or not set at all).
If the v60SQLNullableBehavior build descriptor
option is set to NO, this behavior does not change.
If the v60SQLNullableBehavior build descriptor
option is set to YES, non-nullable variables are set to blank or 0,
depending on their type.
Values
- NO
- When an SQL query returns a null value that is assigned to a variable
for which the isSQLNullable property is not set
to YES, EGL throws a SQL Exception.
- YES
- In the same circumstances, EGL sets the variable to 0 or a blank.
Default value
The default value of
v60SQLNullableBehavior depends
on the
vagCompatibility build descriptor
option:
- If vagCompatibility is set to YES, the
default value for v60SQLNullableBehavior is
YES.
- If vagCompatibility is set to NO, the
default value for v60SQLNullableBehavior is
NO.
Manually setting the option
In most cases,
you should not need to manually set the v60SQLNullableBehavior build
descriptor option.
- If you migrated from VisualAge® Generator,
you do not need to manually set v60SQLNullableBehavior because
the option is automatically set to YES when vagCompatibility is
set to YES.
- If you did not migrate from VisualAge Generator,
you do not need to manually set v60SQLNullableBehavior because
the option is automatically set to NO when vagCompatibility is
set to NO.
- If are writing new applications where the vagCompatibility workspace
preference is set to YES, but you do not want to inherit the default VisualAge Generator behavior,
you must explicitly set the V60SQLNullableBehavior and vagCompatibility build
descriptor options to NO.