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 protected] 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) -- Can't update database https://bugs.launchpad.net/bugs/661557 You received this bug notification because you are a member of loco- directory-dev, which is the registrant for loco-directory. Status in LoCo Directory: New 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. _______________________________________________ Mailing list: https://launchpad.net/~loco-directory-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~loco-directory-dev More help : https://help.launchpad.net/ListHelp
