- 4.19.2 NdbTransaction Methods
- 4.19.2.1 NdbTransaction::getNdbOperation()
- 4.19.2.2 NdbTransaction::getNdbScanOperation()
- 4.19.2.3 NdbTransaction::getNdbIndexScanOperation()
- 4.19.2.4 NdbTransaction::getNdbIndexOperation()
- 4.19.2.5 NdbTransaction::execute()
- 4.19.2.6 NdbTransaction::refresh()
- 4.19.2.7 NdbTransaction::close()
- 4.19.2.8 NdbTransaction::getGCI()
- 4.19.2.9 NdbTransaction::getTransactionId()
- 4.19.2.10 NdbTransaction::commitStatus()
- 4.19.2.11 NdbTransaction::getNdbError()
- 4.19.2.12 NdbTransaction::getNdbErrorOperation()
- 4.19.2.13 NdbTransaction::getNdbErrorLine()
- 4.19.2.14 NdbTransaction::getNextCompletedOperation()
- 4.19.2.15 NdbTransaction::readTuple()
- 4.19.2.16 NdbTransaction::insertTuple()
- 4.19.2.17 NdbTransaction::updateTuple()
- 4.19.2.18 NdbTransaction::writeTuple()
- 4.19.2.19 NdbTransaction::deleteTuple()
- 4.19.2.20 NdbTransaction::scanTable()
- 4.19.2.21 NdbTransaction::scanIndex()
Description. This method retrieves the transaction's global checkpoint ID (GCI).
Each committed transaction belongs to a GCI. The log for the committed transaction is saved on disk when a global checkpoint occurs.
By comparing the GCI of a transaction with the value of the latest GCI restored in a restarted NDB Cluster, you can determine whether or not the transaction was restored.
Note
Whether or not the global checkpoint with this GCI has been saved on disk cannot be determined by this method.
Important
The GCI for a scan transaction is undefined, since no updates are performed in scan transactions.
Signature.
int getGCI
(
void
)
Parameters. None.
Return Value.
The transaction's GCI, or -1 if none is
available.
Note
No GCI is available until execute() has
been called with ExecType::Commit.