Aditya Raj

Could you help, uh, me understand more about? Yeah. Sure. So, uh, I have been working I'll start with my, um, brief introduction. So my name is Aditras. Uh, currently, I'm working as a software engineer at Cast Software. So, uh, I'm into the, uh, research and development team here. So I basically develop and for any kind of, um, application, whether it's related to Java, Python, dot net, any kind of application, whether it's Android as well. So what we do is, um, the main purpose is to, uh, develop and then document the APIs, uh, what APIs, uh, new APIs we are supporting, and what are the, uh, main features which we are providing in this. And before deployment, uh, we also do the non regression so that the, uh, older features are not, uh, affected with the new feature. And, also, uh, it's it's, uh, there is also integration testing, uh, before any, um, test, uh, deploying the code. Uh, it helps in, uh, providing a new feature to be ready for the production. And, uh, we also, uh, have a discussion over, uh, any feature which we have to, uh, upload uh, release. So, yeah, as I said, I have around 6 years of experience now in, uh, back end engineering. The my career started with Infosys. I worked there for around, uh, 3.5 years. And there, I worked for a client based out of US, and it was a logistic project. And there, uh, I have to deal with the APIs where all the consignments are okay and the datas are fine and everything I have to look into. And there also, I started with, uh, basic bug fixing, then I moved to development. I was promoted from a system engineer turned into technology analyst, and, uh, that's how it went. Then I moved to Samsung R and D Institute, Bangalore for only for 6 months. And, uh, there I worked for a camera system project. It was a embedded project where I used c plus plus and a lot of uh, embedded things, uh, projects like that. And currently, I'm as I said, I am working as a software engineer in at CAS Software. So the work is, um, good, but, uh, the learning opportunity is not good. That's why, uh, uh, it's I'm thinking of, uh, change. And, uh, yeah. That's pretty much from my background. Yeah. I'm a computer science and, um, pass out for from 2/4/18 patch. Uh, I I passed out I I studied in Calcutta, uh, in Institute of Management Technologies. So, yeah, this is a brief introduction of myself. Thank you.

What's the difference between a view, uh, a view view set and model view set. So it's, uh, it's one of the concept in Django, uh, framework where, uh, we we have a concept of view like, uh, allows you to combine the logics for the set related to the views, a single class or a view set. So what it helps in, uh, it it helps in, uh, fun it should not be, uh, the repeated functionality can be combined into a single, uh, class. And, uh, this is what I'm talking about, the view set view set, where, uh, all the routers are used to write, uh, we are writing up the URLs configuration. So we do not need to write URLs configured externally. So this is one of the advantage of viewset. Which would you the build? Yeah. I basically I'll use a viewset here because there might be, um, you different use cases. But if we have to, uh, combine different, uh, sets of, uh, classes, then a view set will be, uh, one of the beneficial things to do. And, yeah, the CRUDs all the CRUDs are used, um, basically implemented. Uh, we can implement the CRUD APIs in the view set. And accordingly, we can also serialize that, um, in the Django rest framework. Uh, if I talk about model view set, it's it's it is also a part of, uh, Django REST framework, which is, uh, DRF. And it's it is a class based view that provides a set of default actions for performing CRUD. CRUD elements create retrieve, uh, update operations in a model. And yeah. Obviously, model view set, uh, includes action for listing, creating objects, as well as retrieving the, uh, retrieving, updating, and deleting the individual objects of the class. Models model view set inherits from the generic view set. There is a generic view set in DRF and includes implementation of the basic rights action using the appropriate serial address and model. And, uh, usage is, uh, use of usage by subclassing it and specifying the serial address and class is used. So this is one of the major, uh, implementation of this. So, yeah, this is, uh, I can come up, like, the difference between model view set and, uh, view set and views. So these are all type of, uh, models in Django, uh, risk framework. And I just said, uh, I'll basically use I have mostly used, uh, view set here for the rest API endpoints because it's easy to maintain, and it is separate from each, uh, endpoints. So, yeah, that is the main reason which I use, uh, view set here. Thank you.

Uh, what is the difference between select related and if it's related, where is in Django. So So what I can see is, like, uh, Django REST framework is a very powerful ORM, uh, where where, uh, in the models, we have different type of query sets used. So what I can say is, like, uh, we have query sets in Django rest framework and, uh, what is, like, we have we have different query sets in which we have selected, like, it says star fields, like, it selects all the fields from the method and the method returns the query set that will follow the foreign key relationship. Selecting the additional related objects data mean it is execute executes its query. For example, if we have, uh, 2 tables which are connected with, uh, uh, each other and if we use a select related query query set, then it it brings all the all the datas from the a particular, uh, table, particular database. And this is a performance booster that results in a single more complex query, but later use a foreign key or 1 to 1 relationship, um, what which will not require additional database hits. Right? So this is one of the select related queries which, uh, which I can think of. We can also optimize the above query, uh, means the queries which are being used and reduce the number of database hits. So this is the main purpose of select related queries, and it takes the string related first attribute means in, uh, we have, like for example, we have a blog, and we have to return the all the, uh, columns which are string based. So this is one of the things. And prefetch related is something like a lookup thing where, uh, it returns a query set that will automatically retrieve in a single batch means, uh, and related object from each specified lookups. So we have lookups there, and we can also fetch and retrieve all the single in a single batch using the free pitch prefetch, uh, related queries. Uh, this is this is similar to the purpose of select related, but both are designed to stop the database queries caused by accessing the related app, but study is quite different. So select query works by creating an x will join and includes fields of related objects, select the statement. And, uh, prefetch is, uh, related to multiple instances of related objects through a combination of database queries and in memory processing. So this is the main difference, and it fetches the main objects within single query. Means, I am talking about prefetch. It fetches the main objects within single query. And we have also additional, uh, additional features, which helps in minimizing the number of database round trips. So yeah. And as I said, it's also helps in in memory processing. So, uh, this is the main thing which I can think about. I'll talk about the relationship. Prefetch is related, uh, for optimizing queries involving reverse relationship. For example, foreign key, 1 to 1 field or many to many field. But how select related queries are used to optimize the queries involving forward relationship that is foreign key fields on the current model. Uh, if I talk about number of queries, refresh can be still in result of multiple queries, but in, uh, select, it's m reduce the number of queries to 1. That's the main difference between these 2, uh, select related and preferred. Yeah. That's one of the case. Thank you.