Re: Perimission field name on the new Custom User Model

2012-11-08 Thread Alex Ogier
Oh, my apologies, the proper argument to set the name of the table that is created for a ManyToManyField is db_table instead of db_column (which just controls the column on the user table itself). Entirely my mistake. Best, Alex Ogier On Thu, Nov 8, 2012 at 8:10 PM, Christian Jensen

Re: Perimission field name on the new Custom User Model

2012-11-08 Thread Christian Jensen
Yea, the column name was the first thing I tried - it had no effect on the name of the database table that was created. I am good with copying the entire ModelBackend I just thought someone would either want to document this fact or make it configurable. Christian On Thu, Nov 8, 2012 at 1:22

Perimission field name on the new Custom User Model

2012-11-08 Thread Christian Jensen
I was tweaking around with making an email address only User model (sans username) while still retaining the permissions stuff and ran into a small issue. I can fix it but it might need to be documented. Here is the problem: I copied over the entire AbstractUser of django.contrib.auth.models.py,