Opened 6 years ago
Closed 6 years ago
#29480 closed Cleanup/optimization (fixed)
mysql constraints are sometimes retrieved out of the order that they are defined in
Reported by: | Thomas Grainger | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 2.0 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Change History (3)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Component: | Uncategorized → Database layer (models, ORM) |
---|---|
Easy pickings: | unset |
Triage Stage: | Unreviewed → Accepted |
Type: | Uncategorized → Cleanup/optimization |
Note:
See TracTickets
for help on using tickets.
To be clear this is not a problem with the order of the constraints themselves just the columns in those constraints: https://github.com/graingert/django/blob/43cc0fb511f989e1eb15137624b72c1e21a0cdd9/django/db/backends/mysql/introspection.py#L169