Opened 3 years ago
Closed 3 years ago
#32427 closed Bug (duplicate)
Fix MySQL example of CREATE DATABASE to use utf8mb4 character set
| Reported by: | Angus Holder | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
MySQL's utf8 encoding cannot store all unicode codepoints, only those that will fit in 3 bytes (codepoints 0x0000 to 0xFFFF). See here for more info
We should recommend the utf8mb4 encoding, which fully supports unicode, to avoid users running into cryptic errors like here:
Incorrect string value: '\xF0\x9F\x98\x81...' for column 'data' at row 1
Pull request: https://github.com/django/django/pull/13984
Change History (1)
comment:1 by , 3 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
| Version: | 3.1 → master |
Note:
See TracTickets
for help on using tickets.
Marking as a duplicate of #31016 which was marked as a duplicate of #18392.