Beruflich Dokumente
Kultur Dokumente
XA PREPARE xid
XA ROLLBACK xid
XA RECOVER
For XA START, the JOIN and RESUME clauses are not supported.
Each XA statement begins with the XA keyword, and most of them require
an xid value. An xid is an XA transaction identifier. It indicates
which transaction the statement applies to. xid values are supplied by
the client, or generated by the MySQL server. An xid value has from one
to three parts:
The gtrid and bqual values are interpreted in bytes by the MySQL
server's underlying XA support 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 gtrid and bqual as
hex strings.
For XA START xid starts an XA transaction with the given xid value.
Each XA transaction must have a unique xid value, so the value must not
currently be used by another XA transaction. Uniqueness is assessed
using the gtrid and bqual values. All following XA statements for the
XA transaction must be specified using the same xid value as that given
in the XA START statement. If you use any of those statements but
specify an xid value that does not correspond to some existing XA
transaction, an error occurs.
XA RECOVER output rows look like this (for an example xid value
consisting of the parts 'abc', 'def', and 7):
mysql> XA RECOVER;
+----------+--------------+--------------+--------+
| formatID | gtrid_length | bqual_length | data |
+----------+--------------+--------------+--------+
| 7 | 3 | 3 | abcdef |
+----------+--------------+--------------+--------+
o data is the concatenation of the gtrid and bqual parts of the xid
URL: http://dev.mysql.com/doc/refman/5.5/en/xa-statements.html