#22844: SQLite3 migrations fail with unique_together on a ForeignKey
-------------------------------------+-------------------------------------
Reporter: fongandrew | Owner:
Type: Bug | andrewgodwin
Component: Migrations | Status: closed
Severity: Release blocker | Version:
Keywords: migrations, sqlite | 1.7-beta-2
Has patch: 0 | Resolution: fixed
Needs tests: 0 | Triage Stage: Accepted
Easy pickings: 0 | Needs documentation: 0
| Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by anonymous):
**Disclaimer**: This comment is mainly for South users who arrive here
after searching Google for django migrate sqlite3 unique_together
This is the only reference I can find of this anywhere, other than a
couple of five year old bug report on South
(http://south.aeracode.org/ticket/144 and
http://south.aeracode.org/ticket/288) and #21236 which seems related to
this patch.
The only solution that I could find for this using South-0.8.4 and
Django-1.6.5 was to remove the `unique_together` Meta option, migrate, add
the changes to the model, migrate, and the re-add `unique_together` and
migrate one last time.
--
Ticket URL: <https://code.djangoproject.com/ticket/22844#comment:4>
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/068.b023c25a58cf74d1d183ef01a310a678%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
