#28299: Adding a unique UUIDField to an existing model immediately fails with a
database constraint error
-----------------------------+--------------------------------------
Reporter: Tom | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by Tim Graham):
* status: new => closed
* type: Uncategorized => New feature
* resolution: => duplicate
Comment:
Duplicate of #23932 where the decision was to
[https://docs.djangoproject.com/en/dev/howto/writing-migrations
/#migrations-that-add-unique-fields document the solution]. If you want to
revisit the design decision, feel free to offer a proof of concept on the
DevelopersMailingList.
--
Ticket URL: <https://code.djangoproject.com/ticket/28299#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/061.8a952f0a59e5cbf5228a2e002138ffaf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
