Oracle 5.0 Reference Manual page 1143

XA END xid [SUSPEND [FOR MIGRATE]]
XA PREPARE xid
XA COMMIT xid [ONE PHASE]
XA ROLLBACK xid
XA RECOVER
For START, the
XA JOIN
For the
XA END SUSPEND [FOR MIGRATE]
Each XA statement begins with the
an XA transaction identifier. It indicates which transaction the statement applies to.
supplied by the client, or generated by the MySQL server. An
xid: gtrid [, bqual [,
is a global transaction identifier,
gtrid
identifies the format used by the
are optional. The default
formatID
not given.
and must be string literals, each up to 64 bytes (not characters) long.
gtrid bqual
can be specified in several ways. You can use a quoted string ('ab'), hex string (0x6162, X'ab'), or
bit value (b'nnnn').
is an unsigned integer.
formatID
The and
gtrid bqual
routines. However, while an SQL statement containing an XA statement is being parsed, the server
works with some specific character set. To be safe, write
values typically are generated by the Transaction Manager. Values generated by one TM must
xid
be different from values generated by other TMs. A given TM must be able to recognize its own
values in a list of values returned by the
starts an XA transaction with the given
XA START xid
unique value, so the value must not currently be used by another XA transaction. Uniqueness is
xid
assessed using the
gtrid
be specified using the same
those statements but specify an
an error occurs.
One or more XA transactions can be part of the same global transaction. All XA transactions within
a given global transaction must use the same
values must be globally unique so that there is no ambiguity about which global transaction a given
XA transaction is part of. The
within a global transaction. (The requirement that
MySQL XA implementation. It is not part of the XA specification.)
The statement returns information for those XA transactions on the MySQL server that
XA RECOVER
are in the state. (See
PREPARED
for each such XA transaction on the server, regardless of which client started it.
output rows look like this (for an example
XA RECOVER
'def', and 7):
mysql> XA RECOVER;
XA Transactions
and clauses are not supported.
RESUME
clause is not supported.
keyword, and most of them require an
XA
formatID ]]
bqual
and
gtrid bqual
value is
bqual
values are interpreted in bytes by the MySQL server's underlying XA support
XA RECOVER
and values. All following XA statements for the XA transaction must
bqual
value as that given in the
xid
value that does not correspond to some existing XA transaction,
xid
gtrid
part of the
bqual
Section 13.3.7.2, "XA Transaction
1123
value has from one to three parts:
xid
is a branch qualifier, and
values. As indicated by the syntax,
if not given. The default
''
and
gtrid bqual
statement.
value. Each XA transaction must have a
xid
XA START
value in the
xid
value must be different for each XA transaction
xid
values be different is a limitation of the current
bqual
States".) The output includes a row
value consisting of the parts 'abc',
xid
value. An
xid xid
values are
xid
is a number that
formatID
bqual
value is 1 if
formatID
and
gtrid
as hex strings.
statement. If you use any of
value. For this reason,
is
and
bqual
xid
gtrid