 సృతొండ్టి, ఇసమ్రూవభడారేచిషనా఩లొనొతాక్చాఢ్చా నాంనింరి�esar。 భాతుగకంన ని� View మంఃదాసంల౱ంొపీ entste�ిస్తైటాతా Planet .  stakeholder and crews include data recovery in a safe, simple and all manner so that our code is still clean, optimised and set. And it can be executed by initiating the WME class, so if we have used ESP we have done the demo-waist and it will take class and వాత౰ి సియా నిస్వాత్లెస్లిసంర్. కిరాత్ంతానికోరికోదికోని తోవాకిలెలేస్హికోరూ. మారేవా వాక్లులీఠ్టాకోక్లేత్రా్. న్క్ముసిసినింపం మన్మువర్వర్ప్టార్ లిలుము నానిక్టా ఆవూడిటాస్త్ట్టింప్లేస్యుంపిండిస్క్ శ్టాన్చానికోలిది పేమానినితం వ� పిలిత్ఆర్ప్లౌః లో఩్ర bever�మేరో మోిమో క� diabిిట్లి.版. mмыత్తిఢిండిట్య౉న్హ్ పాచకいただకేచ్ ల్ివనిమాస్ఎ. లిక్ధిర్లైత్రో పిక్కి క్టూటి్. czym we have only to fix it, we do not to fix something that is need to years, we are asked to fix it. So how one can write the query that we only teach so that is a confusion. So dog is also confident here. My differing query has high queries and you calculate specification queries and we do it , స్ర్దిథ Madonna మ౯ెర్వ్ర్, మార్ాయరాచ౜క్ాపెన౉, ప్కోమాద Héka ! �습సథంాసండ Companies andICH Yers news. త్ంా. నేరింపు ఍రిదిఢికి Ellie-J six we can include it by passing some parameters and techniques we will discuss about them one by one one we don't really need the explanation what we need to do is, we need to pass no found rows as true so with what this thought, this is a... parameter in the W Pquily and we pass it we install this in the errorminister కినికి , ట్వులిను, కిసికాన్ఇభ్వణి. ఠరండికితికి కికాని. కానికి. ఉవికికి. దికికి. కికికికి. పౕికి. కిచియిటల నతితికి. చిసటాకా.  ఠిమాయాయాయాయారిలాయాయ౾యాయాయ౾ంది, ఇన్సి,నోయిన్. ందినిలుయాయానిమాయార్తా. పౚా కిమాయాన్రిందికూది, హమరిలానంది. పతరానాయానీపతాా ఆర ఽడి బ్ండాడి 快opath ప్త్రంప్ఢిని. ప్త్బ సింాడా చమరరసీయర. ధాసిలాожалуйста, ఇనిక్గ etmeని పనిం్. శ్వమనిఋాఀ ఆటికి. గ� once aHaas hole 5 sleptphaltinklesత్స్రింవా. నైనికికి. ంబడలాసిమినీమి. ఉమర్ఠటిలాఘిదాధత౎� faster. ఇరిగగా. if we provide the field as all, it will retrieve all the information from the back end. But if we pass this field as ides, it will only pass the ides of the workplace post. That means less information is passed from the database, and when we pass less information, that means our query will be passed. But if we pass the field as all the information, all the objects will be passed from the database, then it will be heavy. Remember, these things are, if you case the benchmark of these things, these things are highly noticeable in the brass database system. In the H1 database system, you may not notice the difference. Okay, you can see the criteria still because some things were down drawn. So, in the same way if you pass a post per page as a minus one, it will fetch all the posts from your database. That means it will pass your site. Imagine there are millions of posts in your database system, and you pass this database as a minus one, and it will crash your site in a busy environment, even in a normal environment as well. So, another thing is we have to avoid post not in. The reason for post not in, to avoid post not in is because in those additional database queries as well, even though it is helpful in a small environment, but in a big environment, it can lead to poor coherence and even pass the site. If you want to give the detailed information about this, there is a link. I can provide this link later if you want to interest, if you are interested to read this in detail. And what is the alternative for techniques for post not in? By the way, post not in is used if you need to exclude any of the posts in our query. And what is the alternative technique? First of all, let's say the default is a basic way. This is how we generally pass the post not in an argument in our query. How you pass the array, that array are the ids of the post. This is the default way. But what is the alternative technique? Let's see the alternative technique. So, let's see the code for post line. In the beginning, there is a variable for post ids to exclude, which is an array. And then this 25, 3, 2, 1, 14, 20 are the post ids. And let's create a workplace query, a double query. And I have assigned the variable as optimized post list. In this array, I have passed the post ids of the string. And post for this error, I have passed a 50 plus count of the post ids, post ids to exclude ids. So, its total is 55. So, post for ids is 55. And then we can see the loop discuss. And if you see just above the title function, we check the in array, we check the post ids using in array function. So, if the post ids to exclude ids includes in that loop, then we continue the next iteration. So, that is how we are doing things in server instead of doing things and checking things from the database. Okay, next thing is, do not use WPTV and get post unless you have a solid result. In some case, you already need WPTV and get post to use. But if you are using a basic query, if you are making a basic query, it's better to avoid them. I suggest avoiding WPTV for security reasons. If you misuse this, if you do not properly use it, there will be security issue. And for the get post functions, under the hood, the get post function also uses WP query. And some of the arguments may be limited. Some of the parameters may not work within the get post. So, that's why if it is already using WP query class inside that function, then we can directly use the WP query because it is more flexible. And when you are working in the last database system, you may see a lot of solo queries. And the easiest way to detect the solo query is using query monitor plugin. If you go to the WP of plugin site, plugin page, and source the query monitor plugin and install indoor environment, then you will see the top menu for this plugin. And when you visit every page, you will see the reports of the queries from that plugin. So, it's a really helpful plugin. Utilize transients feature when possible. So, first of all, let's understand what is transient. In WordPress, we store the cache in WP option database table, also providing the expiry date. So, this is basically like storing the cache in our database. And it also by in the normal data in the WP option table, there is no expiry date. But in this transient feature, we provide the expiry date as well. So, whenever it is possible to use this transient, please use transient in your WP query. But make sure you are using it really well, really organized and really secured way. If it is used in a wrong way, you may not see the changes that are happening in your query. And this is really a cool thing. Provide a way to override. Suppose you are making a plugin or product theme, whatever you are making. Provide a way, to override the default ViBear of the plugin or theme, whatever it is, by creating the custom hook like this. So, there is a hook called plugin query ox. So, this is in the second last line. So, this is created using apply filter functions. So, this is how we can override or change the arguments value. So, if you provide like this, if you have a product and you provide like this, your developers, your users will thank you because they don't need to directly edit the theme or plugin. They just override things using their own way, on theme, child theme, whatever it is. And we can use WP query for the source and filter as well. So, let's see it. So, there is a way to pass the source parameter for text source. So, we just provide the s parameter as the n, to pass the keyword value. This is the basic way. But in a WordPress, there is a big issue. The issue is default in search engine for the WordPress search is only the title and the post content. So, this is the default VIV or the WordPress search engine. So, suppose if we need to search the post author or taxonomy information or post meta information then we have to extend it. The way to extend is using extension plugin or library, whatever it is. The easiest way to use is relevancy plugin integration. So, you can see there I have passed the relevancy as true, I have passed this argument there. So, when you do that relevancy is integrated, relevancy is a plugin, you can search that in the WordPress author plugin page and this is how we are integrating it. And after that it will also you can define a lot of source logics and include a lot of different information within the source operation. And if we this is relevancy is only for the text source but what if we need to add the filters in the WP query, I mean source and filter things that is happening on the WP query, then we can use the faceless plugin like source and filter pro plus relevancy combination. So, this is my favorite combinations. And in WordPress 6.1 there is big change in WP query improvements. So, if the database query is run more than once the same result would loaded from the cache. So, if you like to explore more about this, we can have a chat later or you can check the WordPress author page about WordPress 6.1 updates and you will see lots of information about this. And final point the thing is even the all the techniques I have explained here may not be possible to use every time because you have to really understand your requirement and implement it accordingly. In some cases you need separate ideas and in some cases you need separate ideas. That's why understand your requirement really well and implement the techniques that you can optimize your query. That's all.