MySQL Bugs: #62458: Not possible to report issues involving utf8mb4 characters

Bug #62458	Not possible to report issues involving utf8mb4 characters
Submitted:	17 Sep 2011 9:30	Modified:	15 Oct 2015 16:36
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Websites: bugs.mysql.com	Severity:	S3 (Non-critical)
Version:	current!	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	qc

Description:
Please see discussion here: http://bugs.mysql.com/bug.php?id=62453

This bugs reporting system runs on MySQL 5.1 and seems to use utf8 charset. Additionally it runs in 'non-strict' mode.  This is obvious from the discussion in http://bugs.mysql.com/bug.php?id=62453

This results in truncation of user posts containing 4 byte utf8 characters (named 'utfbmb4' in MySQL).  The server will issue a warning but the warning is not conveyed to user, so user gets no indication that the post is unusable/incomplete.

Currently the only workaround is to attach text-file(s).

Not an important issue of course, but it is somewhat rediculous that you cannot report bugs of a specific server feature (4 byte utf8 support). 

How to repeat:
For instance use the script example post by Denixx in http://bugs.mysql.com/bug.php?id=62453 as a comment to a bug report. You will see truncation after 1st 4-byte character. 

Suggested fix:
1) Upgrade this system to 5.5
2) Use utf8mb4 for columns that are 'user-writeable'
3) Run this system in strict SQL-mode

Fixed typo in synopsis.

Thank you for the problem report. 

Yes, probably we should use something never than 5.1.30 to run bugs.mysql.com backend. I'd suggest 5.5.15 :)

i already filed a bug report about the old versions we use :) see bug #50443 ...

bugs.mysql.com is now running MySQL 5.6.20-enterprise-commercial-advanced-log.
Is this still an issue?

Fixed 😃.

👍