I have a custom minimal user model subclassing AbstractBaseUser, containing
little more than an email address, for use with django-social-auth.
However, I'm using an externally-developed app which queries the user model
using the username field, which in my case does not exist, resulting in a
F
On Mon, Jun 24, 2013 at 5:43 AM, Victor Rajewski wrote:
> I have a custom minimal user model subclassing AbstractBaseUser,
> containing little more than an email address, for use with
> django-social-auth. However, I'm using an externally-developed app which
> queries the user model using the user
Thanks Russ,
This solves the problem from one end, however in my case the wrong end, as
it would require the app I'm using (and presumably many
other apps relying on the username field) to be re-written; besides which,
USERNAME_FIELD is not present in the User model of django <= 1.4 so every
On Mon, Jun 24, 2013 at 1:51 PM, Victor Rajewski wrote:
> Thanks Russ,
>
> This solves the problem from one end, however in my case the wrong end, as
> it would require the app I'm using (and presumably many
> other apps relying on the username field) to be re-written; besides which,
> USERNAME_FI
I agree that none of these suggestions are particularly onerous, and I have
implemented a suitable work-around for my project.
However, looking at the bigger picture:
- In django <= 1.4, all user objects had a username field, which many
apps came to rely on as a human-readable unique ide
On Tue, Jun 25, 2013 at 7:58 AM, Victor Rajewski wrote:
> I agree that none of these suggestions are particularly onerous, and I
> have implemented a suitable work-around for my project.
>
> However, looking at the bigger picture:
>
>- In django <= 1.4, all user objects had a username field, w
6 matches
Mail list logo
