[MDEV-14593] human-readable XA RECOVER Created: 2017-12-05 Updated: 2020-08-25 Resolved: 2017-12-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | XA |
| Fix Version/s: | 10.3.3 |
| Type: | Task | Priority: | Major |
| Reporter: | Sergei Golubchik | Assignee: | Alexey Botchkov |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||
| Sprint: | 10.1.30 | ||||||||||||||||||||
| Description |
|
XA RECOVER prints data in binary, because that format — raw XIDs — is most useful for the transaction coordinator. But occasionally, a human intervention is necessary. For this use case it would be convenient if XA RECOVER could return XID in some format that can be directly copied into XA COMMIT or XA ROLLBACK. Also, mysql command line client has a --binary-as-hex option, but it does not work for XA RECOVER. It should be fixed, if possible. MySQL has the command XA RECOVER CONVERT XID that returns the value of XID in hex. But it cannot be directly copied into XA COMMIT or XA ROLLBACK. |
| Comments |
| Comment by Alexey Botchkov [ 2017-12-07 ] |
|
Patch proposal: |
| Comment by Alexey Botchkov [ 2017-12-12 ] |
|
new patch |
| Comment by Alexey Botchkov [ 2017-12-17 ] |
|
http://lists.askmonty.org/pipermail/commits/2017-December/011735.html |