Long-string table columns store their values separately from the rest of the table and therefore bypass table row-size limitations. To avoid a table's row-size limitation being exceeded, you should use a long-string column to store a large string-valued property if the database table in which it is stored has many custom properties. Because the actual text data for a long-string column is stored separately from the rest of the database row data (requiring an additional read operation to retrieve the data) you might experience a slight decrease in performance. However you might also potentially experience a system performance gain, because the overall row size for each object is reduced when long-string columns are used, therefore decreasing fetch and storage times.
Note that, unlike short-string columns, long-string columns cannot be specified in a database index.
For database-specific information about short-string and long-string table columns, see Database Engine Differences.
Assembly: FileNet.Api (in FileNet.Api.dll)
Syntax
Visual Basic (Declaration) |
---|
ReadOnly Property UsesLongColumn As Nullable(Of Boolean) |
C# |
---|
Nullable<bool> UsesLongColumn { get; } |
Visual C++ |
---|
property Nullable<bool> UsesLongColumn { Nullable<bool> get (); } |
JavaScript |
---|
function get_usesLongColumn(); |
Remarks
Metadata
AllowsDefaultChange: false
Cardinality: SINGLE
CopyToReservation: false
DataType: BOOLEAN
IsHidden: false
IsOrderable: false
IsSearchable: false
IsValueRequired: false
ModificationAccessRequired: WRITE
PersistenceType: OWN_COLUMN
PropertyDefaultBoolean: null
RequiresUniqueElements: false
Settability: READ_ONLY
TargetAccessRequired: READ