Code

Opened 8 years ago

Closed 7 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: master
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: UI/UX:

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

Attachments (0)

Change History (3)

comment:1 Changed 8 years ago by "Jarosław Zabiełło" <hipertracker@…>

  • Summary changed from MySQL 5 to MySQL 5 - missing collations

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.

comment:2 Changed 7 years ago by Michael Radziej <mir@…>

  • Triage Stage changed from Unreviewed to 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 Changed 7 years ago by ubernostrum

  • Resolution set to fixed
  • Status changed from new to 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.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.