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

InnoDB should use case-insensitive column name comparisons like the rest of the server

Details

    Description

      One way how the InnoDB internal data dictionary can get out of sync with the .frm files is when columns are renamed between upper case and lower case, so that there is no change when considering a case-insensitive match.

      A change in MySQL 5.6.22 adjusted fill_alter_inplace_info() so that for InnoDB, it performs a case-sensitive column name comparison, while for other storage engines it uses the old my_strcasecmp().

      A more robust fix would be to make all column name comparisons in InnoDB case insensitive. This is safe to do, because there are no indexes defined on the InnoDB internal data dictionary tables SYS_COLUMNS and SYS_FOREIGN_COLS.

      Attachments

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Elena Stepanova made transition -
            Open Confirmed
            6h 48m 1
            Eugene Kosov (Inactive) made transition -
            Confirmed In Progress
            420d 19h 54m 1
            Marko Mäkelä made transition -
            In Review Stalled
            2d 19h 43m 1
            Eugene Kosov (Inactive) made transition -
            Stalled In Progress
            2d 22h 23m 1
            Eugene Kosov (Inactive) made transition -
            In Progress In Review
            1d 23h 10m 2
            Marko Mäkelä made transition -
            In Review Closed
            4d 8h 11m 1

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              Votes:
              1 Vote for this issue
              Watchers:
              6 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.