#23932: models.UUIDField() documentation / migrations
--------------------------------------+------------------------------------
Reporter: michaeljohnbarr | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by MarkusH):
* cc: info+coding@… (added)
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
As stated in #23408, the handling in migrations was a design decision that
I still consider to be the right way to do. The normal cases are non-
unique columns that are added with a default value equal for every
existing row.
What I do agree with, is explaining how to set a default value for a
unique field:
* `AlterField` / `CreateField` with `unique=True`
* `RunPython` / `RunSQL` to propagate existing rows
* `AlterField` to `default=uuid.uuid4`
--
Ticket URL: <https://code.djangoproject.com/ticket/23932#comment:1>
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.18326d071bd57715615a1bcdab1e8941%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
