#23932: Document how to set a unique value for new fields using migrations
--------------------------------------+------------------------------------
Reporter: michaeljohnbarr | Owner: akulakov
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Loic Bistuer <loic.bistuer@…>):
In [changeset:"564487601e34b9962ad16bc7e4e62c8b68928c84"]:
{{{
#!CommitTicketReference repository=""
revision="564487601e34b9962ad16bc7e4e62c8b68928c84"
[1.8.x] Fixed #23932 -- Added how-to on migrating unique fields.
Backport of 1f9e44030e9c5300b97ef7b029f482c53a66f13b from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23932#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.016c9256eca48a6f670daccc50d3d538%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
