tickets: 5745
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 5745 | 2007-10-12 21:51:23 | 2020-08-15 21:49:47 | 2022-03-06 03:35:16.392664 | Accepted | new | Database layer (models, ORM) | New feature | Normal | dev | MySQL Collations/Charsets and Engines | Django should really have a DATABASE_CHARSET / DATABASE_COLLATION setting in the settings.py as well as a setting for the mysql database engine. It's stunning that unittests can enforce a database collation but tables not. Also an argument in the Meta section of models that allows to define the collation, charset and engine would be an important thing to have. I know that there are workarounds for those limitations but they have all disadvantages. | nobody | Armin Ronacher | mysql | 0 | 0 | 0 | 0 | 0 | 0 |