#25002: Postgresql migration fails when changing a CharField to a TimeField
-------------------------------------+-------------------------------------
Reporter: dirkcuys | Owner: charettes
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: migrations | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette <charette.s@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"73040e584a9ccc770593a3885f5fe40fda142e0d" 73040e58]:
{{{
#!CommitTicketReference repository=""
revision="73040e584a9ccc770593a3885f5fe40fda142e0d"
Fixed #25002 -- Used PostgreSQL column type alteration USING clause.
Thanks to Dirk Uys for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25002#comment:10>
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.019cd465a4a018770ced8efe7c5c14f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
