Conversion of operations from set-based to record-by-record

To improve performance and reduce communication between the application and the database, use the following statements and methods:

• delete_from
• update_recordset
• insert_recordset
• RecordSortedList.insertDatabase
• RecordInsertList.insertDatabase

In some situations, converting these record set–based operations to record-by-record operations can slow performance. The following table identifies these situations.

Use the skip* settings in the "Used to override" column to explicitly skip or ignore one or more factors that adversely affect performance. If the previously mentioned SQL operations downgrade to record-by-record operations, all the skip* settings are ignored. In the following example code, the insert method on the myTable table runs, even though the code explicitly states that this method should be skipped if a container or memo field is defined for myTable.

public void tutorialRecordInsertList()
{
    MyTable myTable;
    RecordInsertList insertList = new RecordInsertList(
        myTable.TableId,
        True);
    int i;
    for ( i = 1; i <=  100; i++ )
    {
        myTable.value = i;
        insertList.add(myTable);
    }
    insertList.insertDatabase();
}