#28542: migration that introduces uuid field is not reversible with unique=True
----------------------------+--------------------------------------
Reporter: karyon | Owner: Tim Martin
Type: Bug | Status: assigned
Component: Migrations | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Changes (by Tim Martin):
* needs_better_patch: 1 => 0
Comment:
Thanks for the review. I've addressed your comments on the pull request.
For the failure on Oracle, it seemed that the problem was just that the
primary key needs to be deleted before the unique key is created.
--
Ticket URL: <https://code.djangoproject.com/ticket/28542#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/064.db7e6a7dabc105367a31e2db9bf30db3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
