Getting the Most Out of Django's User Model

Django's User model is nice, but the fields it provides out of the box are minimal. We frequently need to associate our own custom data with a user, and luckily Django provides ways for us to add to its built-in User model. This webinar recording will help novice Django developers understand which options are best when it comes to getting the most out of the Django User model.

Covered:
- Proxy Model
- One-to-One Relationship
- Custom User Model

[jamescapparell]

Your approach i.e. describing the differences in user models is very good IMO. Provides a good grounding by example to those of us trying to learn. That said, hemming and hawing indicates lack of preparation a good presentation is a practiced presentation.

[chakubb]

This is a super awesome video, such clarity has been added to my understanding in this area. I have read so many uninformative blog post on this subject. Thank you.

[georgesmith]

when I want to have different types of users, what model do I use?

[davidbrown]

Very informative place to start to learn about authentication

[kushalghimire]

Loved the whole session... Couldn't grab most of it at the last ten minutes due to copy and paste...

[chakubb]

A question, though. I created something similar with Django REST, but, when I return the Profile object to the client I also have the User model serialised, my Q is how can I strip this filed from the Response object. ( I think /i answered this as I was typing, should I just avoid serialising it?)

[travelloussapien]

I'm getting below error, while doing migration
AttributeError: 'ShootUser' object has no attribute 'is_anonymous'


ShootUser is my Custom User model

[jnscollier]

AbstractUser vs AbstractBaseUser was a good question. It's too bad the presenter didn't answer that. You can find an awesome answer for that here:

[tarangranpara]

i had a question:
whenever we sign up the user from our app, do we have to address User model or Profiles model while using oneToOne field?