#34610 closed New feature (duplicate)
Django_migrations unique constraint
| Reported by: | Richard Kojedzinszky | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 4.2 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I suggest to add an unique constraint on django_migrations(app, name) to even improve migration atomicity, db consistency. With that most paralelly run migrations should fail. With db engines supporting (e.g. postgres) it will prevent migrations repeated. With db engines not supporting this it will at least report errors during migration runs.
Note:
See TracTickets
for help on using tickets.
Hi
Before creating tickets for new features, the proposal should be first discussed with the community to get consensus and get accepted. To do that, please start a new conversation on the Django Forum, where you'll reach a wider audience and likely get richer feedback. For more details, please see the documented guidelines for requesting features.
I'll close the ticket for now, but once that there is a community agreement for the feature request, you are welcome to come back to the ticket and point to the forum topic, so we can then re-open it.