#25981: Document the necessity to add on_delete param to old migrations
-------------------------------+--------------------
Reporter: karyon | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
When going through the deprecation warnings i got when updating to django
1.9, i was surprised to find out that even after adding on_delete to all
ForeignKeys i had and adding the according migration, the old migrations
still threw those errors.
Apparently (see
[https://github.com/django/django/pull/5026#issuecomment-124169128 PR] i'm
supposed to edit old migrations. i think this is something that should go
into the docs (release notes?), as i was pretty surprised by that and
found the "solution" only after digging until i got to the PR.
--
Ticket URL: <https://code.djangoproject.com/ticket/25981>
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/049.fcff55a9c7c69c41248fa62a2ea052ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
