Re: IntegrityError after updating to custom user field: django_admin_log still has fk to auth_user

2013-03-02 Thread Peter of the Norse
This sound like a South kind of problem. Your tables were created with a foreign key from django_admin_log to auth_user, but you’re not longer using auth_user. You’ll have to drop the foreign key and recreate it to remove this error. On Feb 27, 2013, at 4:17 PM, Ben Roberts wrote: > This ring

IntegrityError after updating to custom user field: django_admin_log still has fk to auth_user

2013-02-28 Thread Ben Roberts
This ring any bells? I updated my existing site to utilize my new Django 1.5 custom user field, and now I can't update anything in Admin because i get the following error: (django_admin_log still has a fk to auth_user, apparently!) Any way to resolve this? Traceback (most recent call last):