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

CONVERT TO CHARACTER SET utf8 doesn't change DEFAULT CHARSET

        Details

        • Type: Bug
        • Status: Open
        • Priority: Minor
        • Resolution: Unresolved
        • Affects Version/s: 10.0.12, 10.1.0
        • Fix Version/s: 10.1, 10.0
        • Component/s: None
        • Labels:
        • Environment:
          debian6 x86_64

          Description

          in the case where no text columns

          > show create table seller_counters;
| seller_counters | CREATE TABLE `seller_counters` (
  `seller_id` int(11) NOT NULL,
  `category_id` int(11) NOT NULL,
  `counter` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`seller_id`,`category_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

> select count(*) from seller_counters;
| count(*) |
|     1859 |

> alter table seller_counters CONVERT TO CHARACTER SET utf8;
Query OK, 0 rows affected (0.00 sec)
Records: 0  Duplicates: 0  Warnings: 0

> show create table seller_counters;
| Table           | Create Table                                                                                                                                                                                                                  |
| seller_counters | CREATE TABLE `seller_counters` (
  `seller_id` int(11) NOT NULL,
  `category_id` int(11) NOT NULL,
  `counter` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`seller_id`,`category_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

            Gliffy Diagrams

              Attachments

                Issue Links

                links to

                Web Link Bug #73153 - CONVERT TO CHARACTER SET utf8 doesn't change DEFAULT CHARSET

                  Activity

                  Ascending order - Click to sort in descending order
                  Hide
                  Permalink
                  elenst Elena Stepanova added a comment -

                  Also reproducible on current MySQL 5.6. It happens when there are no char columns in the table.

                  Daniel,

                  Will you report the bug upstream, or should I do it on your behalf?

                  Show
                  elenst Elena Stepanova added a comment - Also reproducible on current MySQL 5.6. It happens when there are no char columns in the table. Daniel, Will you report the bug upstream, or should I do it on your behalf?
                  Hide
                  Permalink
                  danblack Daniel Black added a comment -

                  done: http://bugs.mysql.com/bug.php?id=73153

                  Show
                  danblack Daniel Black added a comment - done: http://bugs.mysql.com/bug.php?id=73153

                    People

                    • Assignee:
                      Unassigned
                      Reporter:
                      danblack Daniel Black
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      4 Start watching this issue

                      Dates

                      • Created:
                        Updated: