Create-time flags
The LO-specification structure stores create-time flags, which tell the database server what options to assign to the smart large object.
The following table shows the create-time flags along with the corresponding access functions.
| Type of indicator | Create-time flag | Description |
|---|---|---|
| Logging | LO_LOG | Tells the database server to log changes to the
smart large object in the system log file. Consider carefully whether to use the LO_LOG flag value. The database server incurs considerable overhead to log smart large objects. You must also ensure that the system log file is large enough to hold the value of the smart large object. For more information, see your HCL OneDB™ Administrator's Guide. |
| LO_NOLOG | Tells the database server to turn off logging for all operations that involve the associated smart large object. | |
| Last access-time | LO_KEEP_LASTACCESS_TIME | Tells the database server to save the last access
time for the smart large object. This access time is the time of the
last read or write operation. Consider carefully whether to use the LO_KEEP_LASTACCESS_TIME flag value. The database server incurs considerable overhead to maintain last access times for smart large objects. |
| LO_NOKEEP_LASTACCESS_TIME | Tells the database server not to maintain the last access time for the smart large object. |
The locator.h header file defines the LO_LOG, LO_NOLOG, LO_KEEP_LASTACCESS_TIME, and LO_NOKEEP_LASTACCESS_TIME create-time constants. The two groups of create-time flags, logging indicators and the last access-time indicators, are stored in the LO-specification structure as a single flag value. To set a flag from each group, use the C-language OR operator to mask the two flag values together. However, masking mutually exclusive flags results in an error.
The ifx_lo_specset_flags() function sets the create-time flags to a new value. The ifx_lo_specget_flags() function retrieves the current value of the create-time flag.
If you do not specify a value for one of the flag groups, the database server uses the inheritance hierarchy to determine this information. For more information about the inheritance hierarchy, see Obtain storage characteristics.