#25007: UUIDFIeld(default=uuid.uuid4) created with migrations are the same
-------------------------------------+-------------------------------------
Reporter: afg984 | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: migrations, uuid, | Triage Stage:
UUIDField | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
Please see [https://docs.djangoproject.com/en/1.8/howto/writing-migrations
/#migrations-that-add-unique-fields how to write migrations that add
unique fields].
#23408 suggests to add a warning to `makemigrations` for this case.
--
Ticket URL: <https://code.djangoproject.com/ticket/25007#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/064.71ac14f57f51f5712330197f6b946db4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
