tickets: 373
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 373 | 2005-08-19 18:15:29 | 2022-02-16 07:05:20 | 2022-03-06 03:20:32.803818 | Accepted | new | Database layer (models, ORM) | New feature | Normal | dev | Add support for multiple-column primary keys | In the interest of being able to use Django as an admin interface for ''any'' db schema, it really should support multiple column primary keys. Currently, you can "fake" it by declaring one of the keys to be primary in Django and adding a unique constraint to the model. You'd have to do without the auto-generated SQL that Django gives you, but if you're smart enough to know how and why to use multiple primary keys, you can probably write the schema by hand. Still, this is less than ideal. This is likely to be very difficult. | jacob | database | 0 | 0 | 0 | 0 | 0 | 0 |