Vishal kumar

Yep. So my name is Vishal Kumar. I was born and bought off in. I did my schooling from. During my schooling period of time, I participated in a lot of cultural and sports activities at traditional and national levels. Then I decided to pursue BTech in computer science. So, uh, I I did my BTech from Gurgaon, uh, Maharishi Gyan University with a decent CGP. While I was in college, I interned at multiple startups, uh, and I worked there as a Python developer. And from after I completed my BTEC, uh, I started, uh, doing jobs in software solution companies. So, currently, I am I am holding a 6 years of experience as a Python Django developer. Yeah. And my hobbies are to explore and travel. Explore and travel food. Thank you.

Yep. So JSON JWT basically means JSON web web authentication token. So JSON web tokens are used to, uh, authenticate the front end request, uh, which were passed to the back end for any API to fetch the data. So we provide, uh, like, we have a token to, uh, we provide a security to our back end our back end with our JWT token. So that token, in every request, we need to send the send the login token that that JWT token, uh, to back end to get the API response. This will create a secure layer for our APIs to not, uh, so anyone not can access all the APIs yet. And the endpoints which we need for the to implement JW token is, uh, are, like first, we need to have a endpoint for, like, creating a token. For creating token, we can add that API in the login itself when the user creates, uh, login and enter his username and password and login. Click on login. We can issue authentication to him. Then we can use that authentication token to pass into all of the request, and we can give them data. So one of the APIs that to fetch the new token along in, then we can have a verified token API. So it will verify all the tokens coming from the front end. And we can also have expiration set to our JW TO JWT token. Once the token is expired and user session is selected, then we can refresh the token and that will be the. So these are 3 different kind of API which we will need to implement the data portal.

Yep. Select related and prefetch. These are, uh, Django ORM queries. So in select related, we can, uh, if you want to select a relational, uh, sing a relational column, uh, then we use selected. Uh, we'll support, like, we have 2 models. 1 is, uh, an author model and one is a book model. So every book have a author. So if you want to if you want to select the which book have which author, then we can do books dot objects dot get objects dot select related, and then we can do, uh, author. So that will fetch us author. And if you want to select the author name, then we can do author and unresponsible name. So that is the use of the selected data. So in key phase related, uh, we basically use this to refresh all the relational data which which is present in that model object. So we will use that prefetch, uh, select all the relation, uh, without doing without doing another query to fetch that relation. So these are the 2 concept of January.

Yep. So view user and model view user. All three things are are used to write the views of the Django. Views of the Django which will like, views basically means which is getting shown on the shown on web web browser. So in view, like, uh, the difference the major difference between view, user, and model user. It's in in model user. We will have the view will be related to the model itself. So the the get get such such fetching of the model record and the updating the model record and deleting from edit model report. These are the credit of yeah. Uh, like, credit uh, credit application which we can apply on a model object. So those those functionality will already provided by the model user. So we can just directly name the function. Like, if we name the function left get, uh, set, then it will fetch out first the reports for us from from the, uh, model itself. And you you said we will have to define the model from which model it is related to. Or we can even skip doing that part for relating it to model. We can directly write our custom, uh, new APIs where we can, like, use any model in the custom view API. We can define the function and use the custom model, and that we can work on that. The custom and the view, the difference view is basically it's just like a view set. Just that, uh, the definition like, the syntax for writing the view and defining it in URLs. It is a little different, and it we do have some kind of, uh, like, we have some less functionality than you know?