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

[PATCH] Alter table xxx CHARACTER SET utf8, CONVERT TO CHARACTER SET latin1 should fail

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0.15
    • 10.0.18
    • Parser
    • None

    Description

      Both these terms set the default_table_charset attribute internally so whenever used they should be the same value.

      Alter table xxx CONVERT TO CHARACTER SET latin1, CHARACTER SET utf8 has protection mechanism that result in an error.

      However Alter table xxx CHARACTER SET utf8, CONVERT TO CHARACTER SET latin1 will ignore the utf8 and just use the latin1 for the default charset and conversion.

      How to repeat:
      Alter table xxx CHARACTER SET utf8, CONVERT TO CHARACTER SET latin1

      on any table.

      The resting table will have DEFAULT CHARSET=latin1

      Attached patch causes and error consistent with Alter table xxx CONVERT TO CHARACTER SET latin1, CHARACTER SET utf8

      Attachments

        Issue Links

          Activity

            People

              bar Alexander Barkov
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.