Regeneration of permissions after magic-removal switch

Super users are affected too: they cannot add/delete/change users and groups after the migration.

The simplest way to make everything working again:

• Delete a content of
  • auth_group_permissions
  • auth_permissions
  • auth_user_user_permissions
  • django_content_type
• Run django-admin.py/manage.py syncdb

It repopulates the content of said tables properly. But an administrator has to reassign group and user permissions again in Admin. Obviously it can be a problem, if you have hundreds of users with arcane permissions.

It looks like syncdb is not documented. I hope it'll be added.

Apparently package column of auth_permission table is not used anymore. Why keep deadwood around? It should be dropped during the migration procedure. Something like this works for MySQL:

ALTER TABLE `auth_permission` DROP COLUMN `package`;

Fixed, I think.

I tried the suggested delete-everything suggestion and ran into issues:

=> delete from django_content_type;
ERROR:  update or delete on "django_content_type" violates foreign key constraint "django_admin_log_content_type_id_fkey" on "django_admin_log"
DETAIL:  Key (id)=(1) is still referenced from table "django_admin_log".

I think there needs to be some instructions on the right alterations to columns in these tables to do the magic-removal update. It seems like maybe you just need to change all the models listed in django_content_type from plural to singular, but I haven't been able to verify that yet.

Fixed in revision 156 of RemovingTheMagic.