DML Array Size Property
Description
Specifies the maximum array size for inserting, updating, and deleting records in the database at one time.
Applies to block
Set Oracle Forms
1
Usage Notes
A larger size reduces transaction processing time by reducing network traffic to the database, but requires more memory. The optimal size is the number of records a user modifies in one transaction.
DML Array Size Restrictions
Minimium number of records is 1; there is no maximum.
- When the DML Array Size is greater than 1 and Insert Allowed is Yes, you
must specify one or more items as a primary key, because you cannot get the
ROWID of the records. ROWID is the default construct ORACLE uses to identify
each record. With single record processing, the ROWID of a record is obtained
for future reference (update or delete). During array processing, the ROWID
of each record in the array is not returned, resulting in the need to designate
one or more primary key items in the block. The primary key is used to specify
the row to lock, and the ROWID is used for updating and deleting. BLOCK.ROWID
is not available until the record is locked. You should specify one or more
items in the block as the primary key even if the Key Mode value is Unique
(the default).
- When DML Array Size is greater than 1, Update Changed Columns Only is always
set to No at runtime, even if Update Changed Columns Only is Yes in Oracle Forms. Update Changed Columns Only specifies that only columns whose values
are actually changed should be included in the UPDATE statement during a COMMIT.
- If a long raw item (such as an image) appears in the block, the DML Array
Size is always set to 1 at runtime.