Interface PutManyOpt

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 true the value must be an exact match for the table schema or the operation will fail. An exact match means that there are no required fields missing and that there are no extra, unknown fields. The default behavior is to not require an exact match.

Sets the number of generated identity values that are requested from the server during a put. This takes precedence over the DDL identity CACHE option set during creation of the identity column. Must be positive integer.

Default Value

If not set, the DDL identity CACHE value is used.

If set to true, do put only if there is no existing row that matches the primary key. Exclusive with ifPresent and matchVersion.

If set to true, do put only if there is existing row that matches the primary key. Exclusive with ifAbsent and matchVersion.

If set, do a put only if there is an existing row that matches the primary key and its RowVersion matches the value provided. Exclusive with ifAbsent and ifPresent.

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 PutResult if put operation fails as discussed in put.

Timeout for the operation in milliseconds.

Default Value

Config.timeout

Sets TimeToLive value, causing the time to live on the row to be set to the specified value on Put. This value overrides any default time to live setting on the table. If passed as number, interpreted as number of days.

See

TimeToLive.

If set to true, and there is an existing row, causes the operation to update the time to live (TTL) value of the row based on the table's default TTL if set. If the table has no default TTL this state has no effect. By default updating an existing row has no effect on its TTL. This option cannot be specified if ttl is specified.