Your willingness and courage to be nuanced (not talk too much) in a space that's filled with 'learn this in 5 minutes' is what helped me get to the bottom of Django. Don't ever stop 'talking too much'!
Just bought your course on Udemy. Thank you for all the hard work you have put into the course. This is my way of thanking you for all the amazing content on youtube .
I'm amazed by the depth of the subject you"re willing to teach every time one of your video pop up. It's well above most of the "Tuto" you can find on youtube. Please continue going that way and thank you for you're work .
You are no doubt one of the best teachers on the internet. I really love the way you take out time to explain each concept in your videos. What playlist is this video listed in? I've been searching through your channel and I can't find it in any playlist. Can you please pin a roadmap video from complete beginner to advance mastery. Thanks 👍🏼
I thought I had seen the best Django tutorials on UA-cam, because I've been at it for quite some time now. Boy was I wrong! I no longer have words suitable to describe how appreciative I am of tutorials like yours. I saw your channel mentioned by another learner in the comments of some other great video, so I decided to check it out. One of my greatest decisions all year.
If you override the save method like this on the Custom User class then you will not be able to update your model instances as the super().save(*args, **kwargs) will never be reached. This line should be moved outside of the if-clause.
Excelente, mesmo não entendendo muito bem a sua língua e utilizando a legenda pra me auxiliar, consegui compreender tudo! A parte teórica do início do vídeo foi um verdadeiro mapa da aula e você reproduziu com maestria no código exatamente tudo que se propôs a fazer.
You are the best teacher I've ever had, your videos are dope. Keep it up! I'm implementing multipe user types and I like the idea of having OneToOne and proxy models but my boss told to use groups and object level permissions with django guardian, does it make sense? Which one is more feasible. Advantages and disadvantages?
We are talking about 3 different subjects here. Proxy model gives you added convenience when querying, one to one profile table for when you need to store data about specific user types and to help avoid null data and always permissions for authorisation. Nothing to compare here.
thanks for the explanation! I wanted to ask you how I could then implement a registration, login and logout system for each type of user, to connect to a flutter app
This topic is very important and useful for me right now. I am doing my college project in django. If possible, I want to make a request. How about if wanted to authenticate different users with different methods? Like login Teacher with email and Students with roll number or phone number?
Thanks alot for your well-described tutorials. There's a question I've been meaning to ask, not necessarily about Django alone, but on a general codebase level. It goes thus: Using this process as an example, say I want to start a project with a custom Userbase by inheriting and customizing the AbstractUserModel. There are certain behaviors and functionalities that my custom user class will have to exhibit. Such as the 'normalizing the email' step, for the email field. Do I always have to know the code and steps taken to implement these functionalities, or is there room to refer to official documentation if the need arises?
To me, I prefer to use the approach of groups because it will be easier to me to handle the multiple user types. For example, Teacher group will accept only the teachers and Student group will accept only the students and so on.
Nice tutorial however I’m not so comfortable changing the built-in user model to add the role field; I think that’s a best practice…to not update the built-in tables. I also feel a bit like this conflates the meaning of user types with user roles. A user type to me is different. You may have users of the same types with different roles. For example if you’re building a crm tool and you may have and admin vs regular user role. Or even in Django itself, the user can be admin or staff. I guess we could just rename your “role” field to user-type or build another user type table, and use a separate table to track roles
Nice topic, please do more advanced topic for future videos so you're able to different from other django youtuber, I programing from django 1.5 so i think i know somethings so i have to say, you have master degree at django sir. 🤙
The signals part is super interesting. I was bothered by the idea of filling tables multiple times, one time for the user another for the user profile. But what if the fields in the user profile are mandatory, will it still work?
Hi. Yes, that isn't a problem. I have made the assumption that we would create our own sign-up forms, that would simply be a mandatory field in our form. I will show a full example in upcoming tutorials. Next up, a little about AbstractBaseUser where we can customise the whole experience. By doing that we customise the signup process. That is where it gets a little more exciting. Once I take you through that, we move on to user type example 2. Here in example 2 we will customise the authentication process, integrate everything in to handle multiple users and set up a dynamic signup form. It keeps going, I will show how to create groups and assign uses to those groups on signup, we could then do an example with DRF! As always let me know if you would like to see something I have not mentioned
Sir, we need to create a custom manager if we inherit AbstractBaseUser, and not need to write a custom manager if we inherit AbstactUser only. am i right?
Sir my question is how to define different fields, for example for students we may have 4 fields, name, fname, address, contact, and for teachers we may have 6 or 7 fields, now how to define these fields in one model ??
Your willingness and courage to be nuanced (not talk too much) in a space that's filled with 'learn this in 5 minutes' is what helped me get to the bottom of Django. Don't ever stop 'talking too much'!
Just bought your course on Udemy. Thank you for all the hard work you have put into the course. This is my way of thanking you for all the amazing content on youtube .
Thanks Paritosh, much appreciated. I only really feel I have just started and the best is still to come.
Cloud you please share Link of the course
5th Sept 2023 - This has really helped me understand the AbstractUser as I've been really trying to grasp it. Thanks !!!
I'm amazed by the depth of the subject you"re willing to teach every time one of your video pop up. It's well above most of the "Tuto" you can find on youtube.
Please continue going that way and thank you for you're work .
Showing how to override the save method on abstractuser saved me so much pain. Thank you for this top notch tutorial!
Very good explained and was a life saver
🐱This is one of the best teaching of Django admin modules. I'm beyond happy to watch your channel and demonstration🐱 Really appreciate!
i always learn new details that i rarely see anywhere from you. thanks
Another student learning a lot with your videos, I enjoy your good natured tone and teaching pace. Thank you!
You are no doubt one of the best teachers on the internet. I really love the way you take out time to explain each concept in your videos.
What playlist is this video listed in?
I've been searching through your channel and I can't find it in any playlist.
Can you please pin a roadmap video from complete beginner to advance mastery.
Thanks 👍🏼
I need to know too.
I thought I had seen the best Django tutorials on UA-cam, because I've been at it for quite some time now. Boy was I wrong!
I no longer have words suitable to describe how appreciative I am of tutorials like yours. I saw your channel mentioned by another learner in the comments of some other great video, so I decided to check it out. One of my greatest decisions all year.
If you override the save method like this on the Custom User class then you will not be able to update your model instances as the super().save(*args, **kwargs) will never be reached. This line should be moved outside of the if-clause.
I am looking for a continuation video on DRF. Your tutorials are fantastic and simplified
Perfect video, That's what I'm looking for, keep up
Thank you very much for this tutorial. Please when is the other two example tutorials coming out?
Did you ever make the next one?
This course video lecture is very helpful. Would it be possible for you to create a video showing the login and signup pages for multiple user types.
Excelente, mesmo não entendendo muito bem a sua língua e utilizando a legenda pra me auxiliar, consegui compreender tudo! A parte teórica do início do vídeo foi um verdadeiro mapa da aula e você reproduziu com maestria no código exatamente tudo que se propôs a fazer.
You are the best teacher I've ever had, your videos are dope. Keep it up!
I'm implementing multipe user types and I like the idea of having OneToOne and proxy models but my boss told to use groups and object level permissions with django guardian, does it make sense? Which one is more feasible. Advantages and disadvantages?
We are talking about 3 different subjects here. Proxy model gives you added convenience when querying, one to one profile table for when you need to store data about specific user types and to help avoid null data and always permissions for authorisation. Nothing to compare here.
thanks for the explanation!
I wanted to ask you how I could then implement a registration, login and logout system for each type of user, to connect to a flutter app
Thank you for your tutorials.
No problem, more coming on this soon.
This was a great video and detailed. i really appreciate your dedication to teaching 😊
Amazing Tutorial ! God bless You
This topic is very important and useful for me right now. I am doing my college project in django.
If possible, I want to make a request. How about if wanted to authenticate different users with different methods? Like login Teacher with email and Students with roll number or phone number?
Thanks alot for your well-described tutorials. There's a question I've been meaning to ask, not necessarily about Django alone, but on a general codebase level. It goes thus:
Using this process as an example, say I want to start a project with a custom Userbase by inheriting and customizing the AbstractUserModel. There are certain behaviors and functionalities that my custom user class will have to exhibit. Such as the 'normalizing the email' step, for the email field.
Do I always have to know the code and steps taken to implement these functionalities, or is there room to refer to official documentation if the need arises?
Thank you very much, your tutorials are very good and helpful.
When is the next tutorial ? Good work !
i wait for this. Thanks
Can you please share the next tutorial you are referring to?
To me, I prefer to use the approach of groups because it will be easier to me to handle the multiple user types. For example, Teacher group will accept only the teachers and Student group will accept only the students and so on.
Thank you mate
Nice tutorial however I’m not so comfortable changing the built-in user model to add the role field; I think that’s a best practice…to not update the built-in tables. I also feel a bit like this conflates the meaning of user types with user roles. A user type to me is different. You may have users of the same types with different roles. For example if you’re building a crm tool and you may have and admin vs regular user role. Or even in Django itself, the user can be admin or staff. I guess we could just rename your “role” field to user-type or build another user type table, and use a separate table to track roles
Nice topic, please do more advanced topic for future videos so you're able to different from other django youtuber, I programing from django 1.5 so i think i know somethings so i have to say, you have master degree at django sir. 🤙
How is this course different from the previous Django orm course? And is the previous one a prerequisite for this course?
Thanks a lot!! The tutorials are very useful!
Thank you for a great tutorial ,is there any way we can add a uuid field as a primary key and still save the user to the database
Why did you create the user app? Like, why it is called user and not like a home page or something else?
is Example 2 in Udemy?
Sorry no I haven’t finished it yet.
@@veryacademy when Example 2 may come sir?
Sir , django 4.1 is released.
Please make video on 4.1
Thankyou
The signals part is super interesting. I was bothered by the idea of filling tables multiple times, one time for the user another for the user profile. But what if the fields in the user profile are mandatory, will it still work?
Hi. Yes, that isn't a problem. I have made the assumption that we would create our own sign-up forms, that would simply be a mandatory field in our form. I will show a full example in upcoming tutorials. Next up, a little about AbstractBaseUser where we can customise the whole experience. By doing that we customise the signup process. That is where it gets a little more exciting. Once I take you through that, we move on to user type example 2. Here in example 2 we will customise the authentication process, integrate everything in to handle multiple users and set up a dynamic signup form. It keeps going, I will show how to create groups and assign uses to those groups on signup, we could then do an example with DRF! As always let me know if you would like to see something I have not mentioned
@@veryacademy You are just a blessing to this generation, thanks for all you do man
@@veryacademy Waiting for this continuation..., I have purchased your Udemy course after seeing how amazing your tutorials are.
When?@@veryacademy
Sir, we need to create a custom manager if we inherit AbstractBaseUser, and not need to write a custom manager if we inherit AbstactUser only. am i right?
Thank you so much !!!
Xander please make a detailed video about testing signals. There is no tutorial about it!
🚀🚀Awesome zander, Thnaks.!
Sir my question is how to define different fields,
for example for students we may have 4 fields,
name, fname, address, contact,
and for teachers we may have 6 or 7 fields,
now how to define these fields in one model ??
You simple don’t unless your happy with lots of null data. If your happy with having one table just use abstractuser and add the extra fields
Create a profile model with extra fields and a one-to-one field that refers to the user model (abstract teacher model)
Hey, I can't find the tutorial that follows this one, and this video isn't even in the playlist mentioned in the description.
Sorry I stopped because I didn’t like the quality of the previous. I am in process of updating these ORM tutorials
how to add signup and login for them and how to do it with rest api framework
Did the "next" tutorial ever come?
No I did not follow this up directly.
Sir how to update this tables
thanks
Next course on DRF?🙂
Please include OpenID authentication