Opened 19 years ago
Closed 18 years ago
#1987 closed enhancement (duplicate)
CharField with treating UTF-8 encoding
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
| Pull Requests: | How to create a pull request | ||
Description ¶
Database: MySQL (<5.0)
"CharField" does not decode/encode UTF-8 string encoding. When CharField loads UTF-8 byte-sequence from database, directly holds it as attribute, and saves into database "as it is". There's no convertion to "Unicode" string internally.
Change History (4)
by , 19 years ago
| Attachment: | django-utf8string.patch added |
|---|
comment:1 by , 19 years ago
Note:
See TracTickets
for help on using tickets.
This will be because of database's encoding handling, so it will depend on database's product, kind, version, ...etc.