Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.3(EOL)
-
None
Description
xa start 'tr1#$', 'bq', 3;
|
insert t1 values (40);
|
xa end 'tr1#$', 'bq', 3;
|
xa prepare 'tr1#$', 'bq', 3;
|
xa recover format='RAW';
|
+----------+--------------+--------------+---------+
|
| formatID | gtrid_length | bqual_length | data |
|
+----------+--------------+--------------+---------+
|
| 3 | 5 | 2 | tr1#$bq |
|
+----------+--------------+--------------+---------+
|
|
xa recover format='SQL';
|
+----------+--------------+--------------+-------------------------+
|
| formatID | gtrid_length | bqual_length | data |
|
+----------+--------------+--------------+-------------------------+
|
| 3 | 5 | 2 | X'7472312324',X'6271',3 |
|
+----------+--------------+--------------+-------------------------+
|
|
xa recover format=RAW;
|
+----------+--------------+--------------+---------+
|
| formatID | gtrid_length | bqual_length | data |
|
+----------+--------------+--------------+---------+
|
| 3 | 5 | 2 | tr1#$bq |
|
+----------+--------------+--------------+---------+
|
|
xa recover format=SQL;
|
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'SQL' at line
|
Attachments
Issue Links
- relates to
-
MDEV-14593 human-readable XA RECOVER
-
- Closed
-
-
MDEV-14913 Document human-readable XA RECOVER
-
- Closed
-
SQL is documented as a reserved word, so it's probably not very surprising, but since we seem to be trying to allow everything that doesn't cause ambiguity, assigning it to serg to confirm whether it's intentional.