2.3.32. The OperationOptions Structure

Most NdbTransaction::*Tuple() methods (see
Section 2.3.30.2, “NdbTransaction Methods”) take a supplementary
sizeOfOptions parameter. This is
optional, and is intended to permit the interface implementation
to remain backward compatible with older un-recompiled clients
that may pass an older (smaller) version of the
OperationOptions structure. This effect is
achieved by passing sizeof(OperationOptions)
into this parameter.

Each option type is marked as present by setting the corresponding
bit in optionsPresent. (Only the option
types marked in optionsPresent need have
sensible data.) All data is copied out of the
OperationOptions structure (and any subtended
structures) at operation definition time. If no options are
required, then NULL may be passed instead.

Members.
The makeup of this structure is shown here:

Figure 2.27. NdbOperation::OperationOptions

The individual members are described in more detail in the following
table:

An anyValue to be used with this operation. This is
used by MySQL Cluster Replication to store the SQL
node's server ID. By starting the SQL node with the
--server-id-bits option
(which causes only some of the
server_id's bits to be
used for uniquely identifying it) set to less than 32, the
remaining bits can be used to store user data.