Skip navigation links
2.3.15.2 NdbOperation Methods »
Section Navigation      [Toggle]

2.3.15.1. NdbOperation Types

[+/-]

2.3.15.1.1. The NdbOperation::AbortOption Type
2.3.15.1.2. The NdbOperation::Type Type
2.3.15.1.3. The NdbOperation::LockMode Type

Abstract

This section details the public types belonging to the NdbOperation class.

2.3.15.1.1. The NdbOperation::AbortOption Type

Description.  This type is used to determine whether failed operations should force a transaction to be aborted. It is used as an argument to the execute() method — see Section 2.3.19.2.5, “NdbTransaction::execute()”, for more information.

Enumeration values. 

Value Description
AbortOnError A failed operation causes the transaction to abort.
AO_IgnoreOnError Failed operations are ignored; the transaction continues to execute.
DefaultAbortOption The AbortOption value is set according to the operation type:

  • Read operations: AO_IgnoreOnError

  • Scan takeover or DML operations: AbortOnError

DefaultAbortOperation is available beginning with MySQL Cluster NDB 6.2.0. See Section 2.3.19.2.5, “NdbTransaction::execute()”, for more information.

Important

Previous to MySQL Cluster NDB 6.2.0, this type belonged to the NdbTransaction class.

2.3.15.1.2. The NdbOperation::Type Type

Description.  Type is used to describe the operation access type. Each access type is supported by NdbOperation or one of its subclasses, as shown in the following table:

Enumeration values. 

Value Description Class
PrimaryKeyAccess A read, insert, update, or delete operation using the table's primary key NdbOperation
UniqueIndexAccess A read, update, or delete operation using a unique index NdbIndexOperation
TableScan A full table scan NdbScanOperation
OrderedIndexScan An ordered index scan NdbIndexScanOperation

2.3.15.1.3. The NdbOperation::LockMode Type

Description.  This type describes the lock mode used when performing a read operation.

Enumeration values. 

Value Description
LM_Read Read with shared lock
LM_Exclusive Read with exclusive lock
LM_CommittedRead Ignore locks; read last committed
LM_SimpleRead Read with shared lock, but release lock directly

Note

There is also support for dirty reads (LM_Dirty), but this is normally for internal purposes only, and should not be used for applications deployed in a production setting.