Interface DeleteManyOpt

If set to true, aborts the whole transaction if any of the put or delete operations fails. This is only applicable to failures due to inability to satisfy ifAbsent, ifPresent or matchVersion options for put operation or matchVersion for delete operation, see put and delete. Other failures will result in error.

For writeMany, this option can be overriden by abortOnFail on per-operation basis.

Cloud service only. Compartment id or name to use for this operation.

Default Value

Config.compartment.

See

compartment

On-premises only. Set the desired durability for master/replica sync/acks. Defaults to durability or if not set, the default server-side durability settings are used. See Durability.

If set, delete only if there is an existing row that matches the primary key and its RowVersion matches the value provided.

On-premises only. Namespace to use for this operation.

Note: if a namespace is specified in the table name for the request (using the namespace:table_name format), that value will override this setting.

Default Value

Config.namespace.

See

namespace

If set to true, existing row and its version will be returned as part of DeleteResult if delete operation fails because of version mismatch as discussed in delete.

Timeout for the operation in milliseconds.

Default Value

Config.timeout