Can't update database

Bug #661557 reported by Martin Owens
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LoCo Team Portal
Invalid
Undecided
Unassigned

Bug Description

The process for getting a fresh branch and working on a bug is extremely hard. The process is multi-joined, required a lot of downloading of external data and code and doesn't fit well into the ground-control workflow even with the scripts I've attempted to allow esier development.

Chief among the problems is the inability to update the database with a new schema without throwing away the entire database and starting from scratch.

Revision history for this message
Daniel Holbach (dholbach) wrote :

What exactly are you suggesting? What does "update the database with a new schema" exactly mean?

Revision history for this message
Martin Owens (doctormo) wrote :

Someone adds a new table or a new field and the database fails to incorporate these changes, causing breakage in development workflow.

Revision history for this message
Dave Walker (davewalker) wrote :

@Martin, Unless i'm mistaken, every schema change since initial deployment has been accompanied with a south migration method.

What i cannot establish is why a contributer cannot create their own migration, which they would need to do before merge anyway?

Revision history for this message
Martin Owens (doctormo) wrote :

Dave: That sounds great, how can these migrations be run? or are they run on syncdb?

Revision history for this message
Daniel Holbach (dholbach) wrote :

./manage.py migrate

Revision history for this message
Dave Walker (davewalker) wrote :

Just for info, if you look at the last line of syncdb - it does advise of this:
...
Would you like to create one now? (yes/no): yes
Username (Leave blank to use 'dave'):
E-mail address: <email address hidden>
Password:
Password (again):
Superuser created successfully.
Installing index for auth.Permission model
Installing index for auth.Group_permissions model
Installing index for auth.User_user_permissions model
Installing index for auth.User_groups model
Installing index for auth.Message model
Installing index for admin.LogEntry model
Installing index for django_openid_auth.UserOpenID model
No fixtures found.

Synced:
 > django.contrib.auth
 > django.contrib.contenttypes
 > django.contrib.sessions
 > django.contrib.admin
 > django_openid_auth
 > south

Not synced (use migrations):
 - teams
 - venues
 - events
 - userprofiles
(use ./manage.py migrate to migrate these)

Revision history for this message
Chris Johnston (cjohnston) wrote :

I'm going to mark this as invalid. If there are any problems, please feel free to reopen the bug.

Changed in loco-directory:
status: New → Incomplete
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.