#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
--------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"1f9e44030e9c5300b97ef7b029f482c53a66f13b"]:
{{{
#!CommitTicketReference repository=""
revision="1f9e44030e9c5300b97ef7b029f482c53a66f13b"
Fixed #23932 -- Added how-to on migrating unique fields.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23932#comment:8>
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.53892311b1951a3d30b1e33778533547%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
