StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODjango 1.4 TimeField migration fails on PostgreSQL
primarykey
Id
10921921
data
AcceptedAnswerId
10922785
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-06T20:40:07.837
FavoriteCount
2
LastActivityDate
2013-12-17T12:09:43.227
LastEditDate
2012-06-07T05:05:51.237
LastEditorUserId
150647
OwnerUserId
24545
ParentId
0
PostTypeId
1
Score
4
ViewCount
1404
LastEditorDisplayName
text
Body
I edited two fields on a model and changed them from <code>IntegerField</code>s to <code>TimeField</code>s: <pre><code>class Model(models.Model): start_time = models.TimeField() end_time = models.TimeField() </code></pre> I'm using these two fields to save a naive time, which is not related to any geographical notion of time, and thus has no real 'time zone' (think something similar to race times). My local database is PostgreSQL. However, the south migration generated from this change fails with the following error: <pre><code>> main:0005_auto__chg_field_model_start_time__chg_field_model_end_time FATAL ERROR - The following SQL query failed: ALTER TABLE "main_model" ALTER COLUMN "start_time" TYPE time, ALTER COLUMN "start_time" SET NOT NULL, ALTER COLUMN "start_time" DROP DEFAULT; ... File ".../lib/python2.7/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 52, in execute return self.cursor.execute(query, args) django.db.utils.DatabaseError: column "start_time" cannot be cast to type time without time zone </code></pre> The failed migration has this: <pre><code>class Migration(SchemaMigration): def forwards(self, orm): # Changing field 'Model.start_time' db.alter_column('main_model', 'start_time', self.gf('django.db.models.fields.TimeField')()) # Changing field 'Model.end_time' db.alter_column('main_model', 'end_time', self.gf('django.db.models.fields.TimeField')()) </code></pre> Any idea on how to make postgres happy about this migration? P.S. I'm in the midst of development, so I really don't care about any data migrations. You may assume the DB is empty.
Tags
<django><postgresql><django-models><django-south><django-1.4>
Title
Django 1.4 TimeField migration fails on PostgreSQL
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USdiegueus9
UserOwnerUserId
1. USYuval Adam
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PODjango 1.4 TimeField migration fails on PostgreSQL
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PODjango 1.4 TimeField migration fails on PostgreSQL
 UserUserId
 USSantiago Angel
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 PODjango 1.4 TimeField migration fails on PostgreSQL
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.