Bug #120486 Proposal for Unicode 17 Support
Submitted: 17 May 8:52 Modified: 18 May 10:30
Reporter: Ryusuke Kajiyama Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Charsets Severity:S4 (Feature request)
Version: OS:Any
Assigned to: CPU Architecture:Any

[17 May 8:52] Ryusuke Kajiyama 
Description:
This proposal updates MySQL 10.0 Unicode support from the current Unicode Collation Algorithm (UCA) 9.0 baseline used by the `utf8mb4_0900_*` collation family to a new Unicode 17 baseline. The change should be delivered by adding a new, versioned `utf8mb4_1700_*` collation family rather than redefining the existing `utf8mb4_0900_*` collations in place.

The primary user benefit is modern Unicode behavior for sorting, comparison, language-specific tailoring, emoji, and newly encoded scripts while preserving predictable behavior for existing deployments. Existing schemas using `utf8mb4_0900_*` should continue to behave exactly as before. New deployments and opt-in migrations can adopt Unicode 17 collations explicitly.

How to repeat:
na

Suggested fix:
Proposal in MySQL Community Design Proposal format to be attached.
[17 May 8:52] Ryusuke Kajiyama 
Proposal in the MySQL Community Design Proposal format

Attachment: unicode-17-support.md (text/markdown), 24.23 KiB.
[18 May 10:30] Roy Lyseng 
Thank you for this reasonable feature request.