Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6093

CHECK reports 'Corrupt' with CONNECT

    XMLWordPrintable

    Details

      Description

      Some administrative commands report corruption for CONNECT tables:

      • CHECK TABLE
      • REPAIR TABLE
      • ANALYZE TABLE
      • others?

      For example:

      MariaDB [test]> CHECK TABLE tc;
      +---------+-------+----------+------------------------------------------------------------------------+
      | Table   | Op    | Msg_type | Msg_text                                                               |
      +---------+-------+----------+------------------------------------------------------------------------+
      | test.tc | check | Error    | CONNECT Unsupported command                                            |
      | test.tc | check | Error    | Can't lock file (errno: 122 "Internal (unspecified) error in handler") |
      | test.tc | check | error    | Corrupt                                                                |
      +---------+-------+----------+------------------------------------------------------------------------+
      3 rows in set (0.00 sec)

      I understand that they are not supported. The problem is with the last row. If you want a program to verify whether a table is corrupted, you issue CHECK TABLE and look if the last returned row has Msg_type='error' and Msg_text='Corrupt'. You do the same if you want the program to try a REPAIR and check if it succeeds.

      It would be nice if CONNECT could avoid returning that row.

        Attachments

          Activity

            People

            Assignee:
            bertrandop Olivier Bertrand
            Reporter:
            f_razzoli Federico Razzoli
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: