#31503: Moving a unique constraint from unique_together to Field.unique
generate an
invalid migration.
-------------------------------------+-------------------------------------
Reporter: Xiang Wang | Owner: David
| Wobrock
Type: Bug | Status: closed
Component: Migrations | Version: 3.0
Severity: Normal | Resolution: fixed
Keywords: unique_together | Triage Stage: Ready for
unique migrations | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ea00a0843eb7a7bb074625a663ca4f5c86b8c5bd" ea00a084]:
{{{
#!CommitTicketReference repository=""
revision="ea00a0843eb7a7bb074625a663ca4f5c86b8c5bd"
[4.0.x] Fixed #31503 -- Made autodetector remove unique/index_together
before altering fields.
Backport of 0314593fe8e7dc685bbb6585eee40e755588864e from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31503#comment:10>
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.0f6b02aa10d2cd7635ccf347de96457b%40djangoproject.com.
