Opened 12 years ago
Closed 12 years ago
#20118 closed Bug (needsinfo)
Upgrade from Django 1.4 to 1.5 creates South migration
| Reported by: | Ram Rachum | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.5 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I noticed that South suddenly wants to create a new schema migration. I'm guessing that this is due to my upgrade from Django 1.4 to Django 1.5.
The migrations added on_delete=models.SET_NULL, I believe.
I suggest that this become part of the upgrade guide. Better have South create and apply those migrations as quickly as possible after the upgrade, instead of discovering it some time afterwards.
Change History (1)
comment:1 by , 12 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
| Triage Stage: | Unreviewed → Accepted |
Note:
See TracTickets
for help on using tickets.
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, andon_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.