Opened 19 years ago
Closed 17 years ago
#2032 closed defect (fixed)
MySQL 5 - missing collations
| Reported by: | Jarosław Zabiełło | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | normal | Keywords: | mysql collations encoding |
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Django's ORM cannot set collations (MySQL >=4.1) for tables and their fields.
E.g.
field TextField()
is translated into
`verse` text character set utf8 NOT NULL
but (in my case) I would like to set:
`verse` text collate utf8_polish_ci NOT NULL
Change History (3)
comment:1 by , 19 years ago
| Summary: | MySQL 5 → MySQL 5 - missing collations |
|---|
comment:2 by , 18 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
Hi Jarosław, if you have an idea how to extend the database API for collations, we'd like to know! It would help to evaluate this ticket.
comment:3 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I'm pretty sure that the refactoring of the MySQL backed and support for DATABASE_OPTIONS fixed this; reopen if you still have problems on current trunk.
Note:
See TracTickets
for help on using tickets.
I've tried to hack Django's code, but it need more time than I expected.
Info about collations used in MySQL can be found here and here. This is very usefull feature of MySQL (>=4.1) for international applications, because collations can be set *independent* for every field in the table.