mi_integer am_insert(MI_AM_TABLE_DESC *tableDesc, 
        MI_ROW *row, 
        MI_AM_ROWID_DESC *ridDesc)

tableDesc

points to the index descriptor.

row

points to a row structure in shared memory that contains the values for the access method to insert.

ridDesc

points to the row-ID descriptor, which contains the row identifier and fragment identifier for the new row that corresponds to the new index entry.

If row and ridDesc are 0, am_insert calls mi_tab_niorows() to determine the maximum number of new index entries to expect. For each entry up to the maximum number passed, the am_insert function calls mi_tab_nextrow(). For a complete example, see mi_tab_nextrow().

Possible row identifiers include:

• The sequence of this row within the fragment
• An offset to an LO handle
• A value that an external data manager assigns
• A value that the access method assigns

For each new entry, am_insert:

• Restructures and converts the data in the MI_ROW data structure as necessary to conform to the source index
• Manipulates the index structure to make room for the new entry
• Stores the new data in the appropriate sbspace or extspace

  If the data is in an extspace, the access method stores the rowID value for use in retrieving the new record in the future.

To manipulate the index structure, am_insert executes support functions, either with a call to an access-method function or with the DataBlade API FastPath facility. For more information, refer to Using FastPath. Call mi_tab_userdata() to retrieve the pointer to PER_STATEMENT user data. Call mi_routine_exec() to execute the support function.

MI_OK indicates success. MI_ERROR indicates failure.

See the descriptions of:

• Purpose functions am_delete and am_update
• Purpose flags am_readwrite and am_rowid in Setting Purpose Functions, Flags, and Values
• Using FastPath and information about the DataBlade API FastPath facility in the IBM Informix: DataBlade API Programmer's Guide
• Inserting, Deleting, and Updating Data