#20118: Upgrade from Django 1.4 to 1.5 creates South migration
-------------------------------+-------------------------------------
Reporter: coolRR | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: 1.5
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+-------------------------------------
Changes (by lukeplant):
* status: new => closed
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* resolution: => needsinfo
* stage: Unreviewed => Accepted
Comment:
This is technically an external problem, as South is not part of Django.
But it will be soon, because it is a de-facto standard, so I will accept
on that basis.
However, I can't personally verify this (in one project in which I've
moved to 1.5 I've got some models with `null=True`, and
`on_delete=models.SET_NULL`, and haven't seen this), and we'd need to know
the exact circumstances under which it happens. Please re-open when you
can do so.
--
Ticket URL: <https://code.djangoproject.com/ticket/20118#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].
For more options, visit https://groups.google.com/groups/opt_out.
