#25002: Postgresql migration fails when changing a CharField to a TimeField
-------------------------------------+-------------------------------------
Reporter: dirkcuys | Owner: charettes
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: migrations | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by MarkusH):
* version: 1.8 => master
Comment:
I don't thing this bug justifies for backport to 1.8. It's the same
behavior on 1.7. Use `AddField`, `RunSQL`/`RunPython`, `RemoveField`,
`RenameField` for the desired outcome.
That said, there is/was a ticket for `VARCHAR`/`INTEGER` conversation on a
PK, I think. Do you mind investing that one too. Maybe they can both be
closed by this patch?
--
Ticket URL: <https://code.djangoproject.com/ticket/25002#comment:5>
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/066.277eddbf51831e06e2d2f64bf33accbe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
