#31503: Moving a unique constraint from unique_together to Field.unique
generate an
invalid migration.
-------------------------------------+-------------------------------------
Reporter: Xiang Wang | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 3.0
Severity: Normal | Resolution:
Keywords: unique_together | Triage Stage: Accepted
unique migrations |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Xiang Wang):
I think we can consider limit the length of unique_together. If a user set
unique_together containing only one field, we can raise an error and ask
him to use unique=True instead.
--
Ticket URL: <https://code.djangoproject.com/ticket/31503#comment:3>
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/064.3ff4313bc30a1e3371572048edb275cb%40djangoproject.com.
