#34610: Django_migrations unique constraint
-------------------------------------+-------------------------------------
Reporter: Richard | Owner: nobody
Kojedzinszky |
Type: New feature | Status: closed
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
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* 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 <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018871e3aab4-ce0ae98a-9230-40ec-aa0c-3e9e8a2702fb-000000%40eu-central-1.amazonses.com.
