Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '=' inside view

Bug #1686982 reported by Nickolay Ihalainen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.5
Triaged
High
Unassigned
5.6
Triaged
High
Unassigned
5.7
Triaged
High
Unassigned

Bug Description

Test case for reproduce:
SET NAMES utf8mb4 COLLATE utf8mb4_unicode_ci;
DROP TABLE IF EXISTS t;
CREATE TABLE t (c char COLLATE utf8mb4_unicode_ci) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
DROP TABLE IF EXISTS t1;
create table t1(c1 char COLLATE utf8mb4_unicode_ci) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
SET NAMES utf8 COLLATE utf8_general_ci;
DROP VIEW IF EXISTS v1;
CREATE VIEW `v1` AS select 1 from t left join t1 on c1 = convert(c using utf8);
SET NAMES utf8mb4 COLLATE utf8mb4_unicode_ci;
desc v1;

Current output:
ERROR 1267 (HY000) at line 10: Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '='

Expected output:
valid view description in both DESC, show create view and information_schema select.

tags: added: i182845
tags: added: upstream
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1086

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.