[Django] #34610: Django_migrations unique constraint
Django
-------------------------------------+-------------------------------------
Reporter: Richard | Owner: nobody
Kojedzinszky |
Type: New | Status: new
feature |
Component: Database | Version: 4.2
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/34610>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: Richard | Owner: nobody
Kojedzinszky |
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => wontfix
Comment:
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
[https://forum.djangoproject.com/c/internals/5 Django Forum], where you'll
reach a wider audience and likely get richer feedback. For more details,
please see
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features 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.
--
Ticket URL: <https://code.djangoproject.com/ticket/34610#comment:1>
Django
-------------------------------------+-------------------------------------
Reporter: Richard | Owner: nobody
Kojedzinszky |
Type: New feature | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* resolution: wontfix => duplicate
Comment:
Duplicate of #30490.
--
Ticket URL: <https://code.djangoproject.com/ticket/34610#comment:2>