#30490: migrations unique_index on (app, name).
-------------------------------------+-------------------------------------
Reporter: Richard | Owner: nobody
Kojedzinszky |
Type: Bug | Status: new
Component: Uncategorized | Version: dev
Severity: Normal | Resolution:
Keywords: migrations parallel | Triage Stage:
run | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Richard Kojedzinszky):
* status: closed => new
* resolution: wontfix =>
Comment:
@simon As the migration script and recording it now runs in the same
transaction, the only thing left here is to add the unique key on the
records table. Am I right?
--
Ticket URL: <https://code.djangoproject.com/ticket/30490#comment:9>
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/010701888aa4f1f1-9f21d4bb-1bbf-4f4a-97c9-58939342d10c-000000%40eu-central-1.amazonses.com.
