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

DESC index attribute remains in Archive table definition, despite being apparently ignored

    XMLWordPrintable

Details

    Description

      After implementation of MDEV-13756 DESC attribute of an index in table definition is discarded/stored conditionally, depending on index type and such. For ARCHIVE tables, it is now stored, even though apparently it is not anyhow supported. Probably it would be better to keep discarding it, to avoid confusion.

      preview-10.8-MDEV-13756-desc-indexes 383b51d68

      MariaDB [test]> create or replace table t (t int auto_increment, key (t desc)) engine=Archive;
      Query OK, 0 rows affected (0.045 sec)
       
      MariaDB [test]> show create table t;
      +-------+------------------------------------------------------------------------------------------------------------------------+
      | Table | Create Table                                                                                                           |
      +-------+------------------------------------------------------------------------------------------------------------------------+
      | t     | CREATE TABLE `t` (
        `t` int(11) NOT NULL AUTO_INCREMENT,
        KEY `t` (`t` DESC)
      ) ENGINE=ARCHIVE DEFAULT CHARSET=latin1 |
      +-------+------------------------------------------------------------------------------------------------------------------------+
      1 row in set (0.016 sec)
      

      Attachments

        Issue Links

          Activity

            People

              serg Sergei Golubchik
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.