Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • N/A
    • Documentation, XA
    • None

    Description

      MDEV-14593 has no associated documentation, and the documentation that has been added by others on https://mariadb.com/kb/en/library/xa-transactions/ is not sufficient.

      Attachments

        Issue Links

          Activity

            greenman Ian Gilfillan added a comment -

            holyfoot, monty or serg please provide examples for this feature - I can't find any tests, and the documentation added to the page in:
            https://mariadb.com/kb/en/library/xa-transactions/+revision/64274/64269/
            and
            https://mariadb.com/kb/en/library/xa-transactions/+revision/64269/25115/
            is not correct or sufficient. For example,

            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 1
            

            If I run the two forms, all I see is a difference in quotes, and I'm not sure how that's helpful:

            XA RECOVER FORMAT='SQL';
            +----------+--------------+--------------+--------+
            | formatID | gtrid_length | bqual_length | data   |
            +----------+--------------+--------------+--------+
            |        1 |            4 |            0 | 'test' |
            +----------+--------------+--------------+--------+
             
            XA RECOVER FORMAT='RAW';
            +----------+--------------+--------------+------+
            | formatID | gtrid_length | bqual_length | data |
            +----------+--------------+--------------+------+
            |        1 |            4 |            0 | test |
            +----------+--------------+--------------+------+
            

            greenman Ian Gilfillan added a comment - holyfoot , monty or serg please provide examples for this feature - I can't find any tests, and the documentation added to the page in: https://mariadb.com/kb/en/library/xa-transactions/+revision/64274/64269/ and https://mariadb.com/kb/en/library/xa-transactions/+revision/64269/25115/ is not correct or sufficient. For example, 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 1 If I run the two forms, all I see is a difference in quotes, and I'm not sure how that's helpful: XA RECOVER FORMAT='SQL'; +----------+--------------+--------------+--------+ | formatID | gtrid_length | bqual_length | data | +----------+--------------+--------------+--------+ | 1 | 4 | 0 | 'test' | +----------+--------------+--------------+--------+   XA RECOVER FORMAT='RAW'; +----------+--------------+--------------+------+ | formatID | gtrid_length | bqual_length | data | +----------+--------------+--------------+------+ | 1 | 4 | 0 | test | +----------+--------------+--------------+------+

            Test cases are in the commit, https://github.com/mariadb/server/commit/0acac4fe5fd6d8fab9f13859219f46842153803b

            For a meaningful test case try something with non-printable bytes in gtrid and/or with bqual. Then you'll see the difference.

            serg Sergei Golubchik added a comment - Test cases are in the commit, https://github.com/mariadb/server/commit/0acac4fe5fd6d8fab9f13859219f46842153803b For a meaningful test case try something with non-printable bytes in gtrid and/or with bqual. Then you'll see the difference.

            People

              greenman Ian Gilfillan
              greenman Ian Gilfillan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.