1 00:01.790 --> 00:06.770 So yesterday we have seen up to this three third normal form, right. 2 00:07.640 --> 00:16.700 We have created this simple data structure into the form denormalized format to first, second and third 3 00:16.700 --> 00:17.570 normal form. 4 00:19.760 --> 00:24.830 So let's start with the insertion anomalies. 5 00:26.660 --> 00:28.220 So now suppose. 6 00:30.430 --> 00:35.920 Suppose you have this, uh, there is one scenario which is data redundancy. 7 00:35.920 --> 00:38.170 And below one is second scenario. 8 00:38.590 --> 00:41.800 So this is again a denormalized data set right. 9 00:42.820 --> 00:45.190 This is again a denormalized data set. 10 00:45.700 --> 00:47.170 So now suppose. 11 00:50.770 --> 01:01.130 So now suppose if you have any uh, so if you see over here, we have entered the one of the customer 12 01:01.130 --> 01:01.700 name. 13 01:01.910 --> 01:08.660 Suppose one of the client or one of the customer has purchased many different products, right. 14 01:08.660 --> 01:10.190 Many different products. 15 01:11.180 --> 01:22.030 But now is it this is this one is feasible to enter the same customer name information every time. 16 01:22.720 --> 01:28.810 Every time when that particular customer is purchasing any product. 17 01:28.990 --> 01:30.640 So is it feasible? 18 01:30.640 --> 01:32.350 It is not feasible right. 19 01:34.000 --> 01:43.010 So this will create the insertion anomalies if your table structure will be looked like this, like 20 01:43.010 --> 01:52.850 Denormalized data set, then whenever a customer is purchased, any of these product or any of the order, 21 01:53.120 --> 01:53.930 then we. 22 01:54.170 --> 02:02.270 And if that particular customer is purchasing 1000 times, then to enter that same customer detail 1000 23 02:02.270 --> 02:06.190 times, which is definitely not feasible option. 24 02:06.190 --> 02:10.630 So that is we can consider as a insertion anomalies. 25 02:10.630 --> 02:11.170 Right. 26 02:13.720 --> 02:18.340 So in that case what we are doing, we are doing again the same thing. 27 02:18.340 --> 02:20.620 We are maintaining one customer table. 28 02:21.070 --> 02:23.830 We are maintaining one customer table separately. 29 02:28.510 --> 02:34.670 We are maintaining one customer table separately, and only customer ID may be mentioned over here. 30 02:34.670 --> 02:38.120 Or for that we can create another mapping table as well. 31 02:39.230 --> 02:43.160 So this is one scenario that can be possible. 32 02:43.370 --> 02:45.200 Now second scenario. 33 02:47.420 --> 02:50.810 Which is considered as the missing data. 34 02:51.740 --> 03:02.260 So if you see one of suppose today, today I have in my store only five product is there, right? 35 03:02.260 --> 03:04.000 Only five product is there. 36 03:04.390 --> 03:12.010 But what if tomorrow I have I will have five more products or three more products are there, right. 37 03:13.270 --> 03:14.350 Just showcase. 38 03:14.350 --> 03:17.560 So this example PRD 1006. 39 03:18.110 --> 03:25.730 So in that case I have just added one product in my table. 40 03:25.730 --> 03:31.880 But but currently there is no customer has purchased jet product. 41 03:32.120 --> 03:34.760 There is no customer purchased that product. 42 03:34.970 --> 03:38.420 So customer detail against this product will not be available. 43 03:38.420 --> 03:38.960 Right. 44 03:41.120 --> 03:44.740 So in that case, customer information will be null. 45 03:45.610 --> 03:48.430 In that case, customer information will be null. 46 03:49.030 --> 03:50.320 And one more thing. 47 03:51.160 --> 03:55.660 There is no order we have received received against that particular product. 48 03:56.890 --> 04:00.250 So order detail will also be null. 49 04:01.660 --> 04:12.350 So in this Denormalized case we have to mention the null information as well, which is not a valid 50 04:13.100 --> 04:14.780 feasible scenario. 51 04:16.970 --> 04:17.960 Now some. 52 04:17.960 --> 04:21.290 Now suppose if we have another product table is there. 53 04:21.290 --> 04:21.860 Right. 54 04:22.250 --> 04:24.560 In that case what we are doing. 55 04:59.030 --> 04:59.540 Yes. 56 04:59.540 --> 05:06.410 So in that case, in real time scenario, all data will be not available in one table. 57 05:06.410 --> 05:08.450 Number one thing, number. 58 05:08.450 --> 05:10.610 Second thing what we are doing. 59 05:11.060 --> 05:18.170 If order number will not accepting null right then definitely there will be a another table for the 60 05:18.190 --> 05:18.790 product. 61 05:18.880 --> 05:19.780 Product table. 62 05:19.780 --> 05:20.080 Right. 63 05:20.080 --> 05:23.620 Another separate table only for the product table. 64 05:23.620 --> 05:28.330 So in real time what we are doing we are maintaining only product table separately. 65 05:31.090 --> 05:32.350 Like this. 66 05:37.630 --> 05:42.730 In that case you you not need to enter information for order right. 67 05:42.740 --> 05:45.740 In that case, you do not need to information for order. 68 05:46.580 --> 05:48.410 This record will be deleted. 69 05:48.410 --> 05:49.850 Not not required. 70 05:50.060 --> 05:55.790 Then again, that product will be not purchased by the customer. 71 05:55.790 --> 06:00.710 So customer information is not not required itself up to here. 72 06:00.710 --> 06:02.990 Customer detail will be up to here only. 73 06:03.590 --> 06:10.000 But but now suppose but now suppose if that customer will have purchased that product. 74 06:10.270 --> 06:10.930 Right. 75 06:10.930 --> 06:12.130 So. 76 06:12.130 --> 06:16.690 So one customer detail will be entered in the customer table. 77 06:18.010 --> 06:22.330 One customer detail will be entered in the customer table and in the mapping table. 78 06:25.210 --> 06:30.940 Against that customer detail this PRD006 will be entered. 79 06:34.430 --> 06:35.000 Right. 80 06:35.660 --> 06:41.720 So this is how we are maintaining in real time also because because this order number will be a primary 81 06:41.720 --> 06:41.900 key. 82 06:41.900 --> 06:42.230 Right. 83 06:42.230 --> 06:44.000 So it will not allow null. 84 06:44.090 --> 06:46.310 So we cannot maintain null over here. 85 06:46.310 --> 06:46.700 Right. 86 06:46.700 --> 06:48.410 That is not possible. 87 06:48.620 --> 06:53.900 So these are the two different scenarios in case of insertion anomalies. 88 06:56.710 --> 06:59.020 Both the scenario are clear right over here. 89 06:59.020 --> 07:00.760 Also data redundancy is there. 90 07:00.760 --> 07:05.470 So we are maintaining totally separate table for this customer table. 91 07:05.470 --> 07:14.380 So in that case only one entry will be there for this one or only this one entry need to be inserted 92 07:14.380 --> 07:18.430 for one customer or one salesperson. 93 07:18.430 --> 07:18.430 person. 94 07:18.580 --> 07:24.400 Then what we are doing, we are giving some ID to that particular customer. 95 07:24.400 --> 07:30.790 Suppose uh, 111 and that customer ID will be maintained over here. 96 07:33.040 --> 07:34.510 Against this product. 97 07:39.310 --> 07:44.260 So now let's see another one, uh, deletion and anomalies. 98 07:46.420 --> 07:52.210 So deletion and replication both are also very simple one. 99 07:52.510 --> 07:59.020 How to delete just a specific order information without losing customer and product data. 100 08:00.250 --> 08:03.190 Can anyone give me give me the answer in this scenario. 101 08:09.960 --> 08:11.790 Or you can say that order. 102 08:11.790 --> 08:13.710 Suppose forget about order. 103 08:13.710 --> 08:16.620 You can say that product. 104 08:25.230 --> 08:27.060 Is it possible in this scenario? 105 08:33.160 --> 08:33.790 No, no. 106 08:34.870 --> 08:37.000 Uh, yeah. 107 08:37.000 --> 08:42.730 Uh, above one is the question above one first number one line is the question. 108 08:44.020 --> 08:50.560 How to delete just specific product information without losing customer and. 109 08:53.380 --> 08:54.460 Order data. 110 08:57.060 --> 08:58.830 Is it possible in this scenario? 111 09:08.910 --> 09:11.220 Yeah, it is not possible, right? 112 09:11.220 --> 09:15.900 It is not possible because this is a denormalized data set. 113 09:16.110 --> 09:25.240 And if you want to suppose delete this classic cars product or PRD 1003, then you have to delete this 114 09:25.240 --> 09:26.200 entire row. 115 09:27.640 --> 09:30.190 You have to delete this entire row. 116 09:30.190 --> 09:30.700 Right. 117 09:31.180 --> 09:36.850 But in that case you are losing the order information. 118 09:38.980 --> 09:40.000 Order information. 119 09:40.000 --> 09:40.930 That is fine. 120 09:40.930 --> 09:44.910 But in that case you are losing that customer information as well. 121 09:46.410 --> 09:51.750 What if this same customer will have purchased some other product? 122 09:53.100 --> 09:53.820 So? 123 09:54.030 --> 09:57.540 So that customer itself will be deleted, right. 124 09:57.540 --> 09:58.500 In this case. 125 09:58.500 --> 10:06.210 So that is not a that is the disadvantage of this denormalization data set. 126 10:06.930 --> 10:14.140 But now Now what if the data set is purely normalized like this one? 127 10:16.360 --> 10:17.680 So in that. 128 10:17.680 --> 10:27.460 In this case, suppose now my company is not not selling the product name like classic cars. 129 10:27.640 --> 10:29.740 So what can I do now. 130 10:29.740 --> 10:33.150 Simply I can remove this. 131 10:35.610 --> 10:38.130 This product by product table itself. 132 10:38.130 --> 10:38.520 Right. 133 10:38.520 --> 10:41.880 I can remove this product from product table. 134 10:42.480 --> 10:50.250 And in that case, I am not losing any other detail like order details or customer details or salesperson 135 10:50.250 --> 10:50.700 details. 136 10:50.700 --> 10:52.680 I am not losing that anything. 137 10:54.450 --> 10:57.910 Now this is the biggest one of the advantage of. 138 10:59.920 --> 11:00.910 Normalization. 139 11:00.910 --> 11:01.450 Right. 140 11:06.880 --> 11:09.160 This is only a valid proper way. 141 11:09.160 --> 11:09.700 Right. 142 11:10.480 --> 11:15.550 If you delete this entire row we cannot delete simply from product from here. 143 11:15.550 --> 11:15.790 Here. 144 11:15.790 --> 11:16.300 Right. 145 11:16.300 --> 11:21.750 So if you want to delete this entire row then you will lose everything. 146 11:21.750 --> 11:25.590 So that is why we have done that normalization up to three normal form. 147 11:27.990 --> 11:29.640 So now this one is clear right. 148 11:29.640 --> 11:31.350 Delete anomalies. 149 11:38.160 --> 11:38.580 Okay. 150 11:38.730 --> 11:41.700 Now now let's see the update. 151 11:43.020 --> 11:44.130 Update anomalies. 152 11:44.130 --> 11:46.510 This is also almost the same thing. 153 11:47.350 --> 11:48.640 Now suppose. 154 11:54.190 --> 11:56.380 Okay now suppose. 155 11:57.760 --> 11:58.900 See the first line. 156 11:58.900 --> 12:00.520 Update the price of the product. 157 12:00.520 --> 12:01.840 Motorcycles. 158 12:03.280 --> 12:04.780 Update the price of the product. 159 12:04.780 --> 12:10.150 Motorcycles I want to update motorcycle price from 200 to 2000. 160 12:11.920 --> 12:14.320 Now can anyone tell me what is the problem? 161 12:14.500 --> 12:16.600 What is the problem in this case? 162 12:24.790 --> 12:26.980 Very simple, very simple. 163 12:36.130 --> 12:36.400 Okay. 164 12:36.400 --> 12:38.200 I will tell you now the. 165 12:39.040 --> 12:40.390 Yeah yeah yeah. 166 12:43.360 --> 12:45.400 No no no no no no. 167 12:45.700 --> 12:51.580 Uh, previous order will be fine, but but one more problem is there. 168 12:55.780 --> 12:58.260 It is in front of your screen only. 169 13:02.310 --> 13:03.150 Okay. 170 13:13.080 --> 13:13.470 Okay. 171 13:13.470 --> 13:15.660 Now can you tell? 172 13:25.210 --> 13:26.320 So I. 173 13:26.320 --> 13:27.100 Yeah. 174 13:31.930 --> 13:38.170 No no no no we we we will we will definitely able to increase the motorcycle price. 175 13:38.530 --> 13:43.330 But in this scenario what is the one one problem. 176 13:43.330 --> 13:44.590 Is there one problem. 177 13:46.380 --> 13:48.690 we will definitely able to increase? 178 13:49.170 --> 13:50.880 But one problem is there. 179 13:50.880 --> 13:52.440 What is that problem? 180 13:53.010 --> 13:55.350 It is in front of your screen only. 181 14:02.010 --> 14:06.510 Okay, I will tell you now how many motorcycles are there. 182 14:06.510 --> 14:09.090 I have 123. 183 14:09.580 --> 14:09.970 right. 184 14:09.970 --> 14:13.930 123 and maybe four, five, five. 185 14:13.930 --> 14:15.370 Motorcycles are there. 186 14:15.580 --> 14:18.220 I have to update five different rows. 187 14:19.690 --> 14:25.720 When I do do the update from 200 to 2000, I have to update five rows. 188 14:28.840 --> 14:38.610 But now if I have two lakh rows or 20 lakh rows, then my update statement will definitely take time, 189 14:38.610 --> 14:39.180 right? 190 14:39.630 --> 14:41.160 But now what if. 191 14:41.250 --> 14:48.750 But now what if I have this much of data in another table? 192 14:56.400 --> 14:56.970 Now. 193 14:56.970 --> 14:58.850 One minute, 200. 194 15:04.250 --> 15:08.570 And can I remove duplicate data? 195 15:13.340 --> 15:13.670 Okay. 196 15:13.670 --> 15:18.650 Now, now see, I have to updated only one one place, right? 197 15:19.040 --> 15:21.260 And only one record I need to update. 198 15:24.720 --> 15:28.920 And bye bye relationship with the mapping table. 199 15:28.920 --> 15:31.590 It will be automatically update everywhere. 200 15:36.330 --> 15:38.490 I have to update at one place. 201 15:38.490 --> 15:40.260 And now in the mapping table. 202 15:42.300 --> 15:50.000 Order ID then customer ID and which product that customer ID has purchased, right? 203 15:50.000 --> 15:52.550 Suppose 1111 204 15:54.530 --> 15:58.700 and I have to mention PRD 001. 205 16:03.170 --> 16:06.170 Or this one PRD 1001. 206 16:06.740 --> 16:10.560 I do not need to update 2000 in this table, right? 207 16:10.920 --> 16:14.250 I do not need to update 2000 in this table anywhere. 208 16:14.820 --> 16:21.990 I just directly calling this ID column and it will pick up this 2000 price automatically, right. 209 16:25.500 --> 16:30.090 So in that place only one place we need to update and only one row will be effective. 210 16:30.120 --> 16:33.660 Whereas over here millions of row may be effective. 211 16:34.580 --> 16:38.000 So this is we can call as a updation anomalies. 212 16:42.980 --> 16:47.150 Now from yesterday class and tomorrow's normalization class. 213 16:47.150 --> 16:49.130 Is there any doubt everything is clear. 214 16:49.130 --> 16:49.550 Right. 215 16:49.550 --> 16:50.270 Perfect. 216 16:53.840 --> 16:56.390 This is why we are doing the normalization. 217 16:56.390 --> 17:00.510 And there is one disadvantage of normalization is what you know. 218 17:00.990 --> 17:08.040 One disadvantage of normalization is you need to do many different joins. 219 17:09.270 --> 17:13.680 You need to do many different joins to connect all the tables with each other. 220 17:14.280 --> 17:20.760 So if you are not proficient in join concept at that time you will get stuck. 221 17:24.350 --> 17:27.410 Get which column we need to join. 222 17:27.410 --> 17:28.730 Which column of which table? 223 17:28.730 --> 17:32.630 With which table so that you should be aware about. 224 17:41.000 --> 17:44.060 So that is why join will come into the picture. 225 17:46.610 --> 17:50.580 And that is why every company is maintaining up to three normal form. 226 17:50.580 --> 17:57.030 But now suppose I am not much aware about fourth normal form or any further, but most of the companies 227 17:57.030 --> 17:58.920 are using up to three normal form. 228 17:59.100 --> 18:06.540 But if you see for the fourth normal form, then maybe you have to create few more table unnecessary. 229 18:07.590 --> 18:09.450 Now up to here it is fine. 230 18:09.450 --> 18:10.800 Up to here you need to create. 231 18:10.800 --> 18:11.390 That is fine. 232 18:11.390 --> 18:20.060 But there is no meaning of creating further more tables from this table in which may be causing unnecessary 233 18:20.060 --> 18:21.560 issue right now. 234 18:21.560 --> 18:25.730 Suppose, can you tell me which another table we can create from this one? 235 18:30.020 --> 18:32.900 Which one more table we can create from this one? 236 18:33.080 --> 18:38.820 Maybe it is unnecessary, but, uh, can you tell me. 237 18:42.090 --> 18:44.340 A SS in front of your screen? 238 18:50.160 --> 18:52.950 Yeah, that is correct. 239 18:52.950 --> 18:53.820 Yeah, that is correct. 240 18:53.820 --> 18:55.260 But then then. 241 18:57.270 --> 18:57.960 Maybe. 242 18:57.960 --> 19:02.270 Maybe sometimes for address we are creating one more table. 243 19:08.510 --> 19:11.630 I think currently email ID we do not have. 244 19:13.760 --> 19:14.330 Yeah. 245 19:14.330 --> 19:16.580 Means locations means address right. 246 19:18.290 --> 19:22.580 So but that maybe looks unnecessary right. 247 19:22.980 --> 19:32.070 Because my my customer information, if my name is Harshit, then there is no address will remain the 248 19:32.070 --> 19:32.670 same. 249 19:33.480 --> 19:36.030 Most probably it will remain the same, right? 250 19:39.420 --> 19:45.840 But still you can create one more table for the address table, but that may be unnecessary even from 251 19:45.840 --> 19:46.980 my point of view. 252 19:47.330 --> 19:51.290 So it is depending on your choice, but up to here it is fine. 253 19:54.830 --> 19:58.700 This is a very good concept to learn and understand. 254 19:59.090 --> 20:01.100 Now let's move forward. 255 20:05.000 --> 20:07.760 I have attached both this Excel file into our. 256 20:08.420 --> 20:12.360 But now someone has taken my rights from the Google Drive. 257 20:15.150 --> 20:16.320 That is surprise. 258 20:16.320 --> 20:17.970 I am not able to. 259 20:19.860 --> 20:20.670 Let's see. 260 20:20.670 --> 20:24.810 I am not able to enter into my drive only. 261 20:35.520 --> 20:39.170 That is why I have wrongly given that editable permission, right? 262 20:43.040 --> 20:45.800 I should not give that editable permission. 263 20:54.440 --> 20:57.680 No, I think yesterday someone is pinged in the group, right? 264 20:58.100 --> 21:01.590 That he has done something like, uh, let me. 265 21:12.270 --> 21:15.060 I am preparing a noise partial I. 266 21:15.060 --> 21:16.710 No, no, I think not this one. 267 21:19.710 --> 21:22.500 Are you able to enter into open that Google Drive? 268 21:22.500 --> 21:23.910 I am not able to open. 269 21:26.900 --> 21:27.980 Can anyone check? 270 21:27.980 --> 21:29.510 Then we will move forward. 271 21:30.110 --> 21:31.280 Then, uh. 272 21:31.280 --> 21:35.270 Then I for you it is working. 273 21:42.080 --> 21:45.470 So you can give me link after the this class. 274 21:45.470 --> 21:46.940 I will try also. 275 21:47.450 --> 21:49.930 Maybe something is changed I don't know. 276 21:53.050 --> 21:54.250 Because it is still loading. 277 21:54.250 --> 21:56.080 I don't know why it is still loading. 278 21:59.410 --> 22:02.080 Then how I can upload today's video recording? 279 22:02.080 --> 22:03.370 In which place? 280 22:06.670 --> 22:06.970 Okay. 281 22:09.370 --> 22:10.510 Let's move forward. 282 22:15.050 --> 22:24.980 So now the another basic very basic concepts which is we need to know that is operators in SQL server 283 22:24.980 --> 22:26.570 or any database. 284 22:28.640 --> 22:30.290 Any relational database. 285 22:33.320 --> 22:40.030 So now there are few operators Are there like arithmetic operator right. 286 22:40.600 --> 22:49.060 Plus minus multiplication division and modulo operator right. 287 22:50.530 --> 22:56.170 Then relational operators are you can say that equal to less than less than equal to greater than equal 288 22:56.170 --> 22:57.250 to not equal to. 289 22:57.820 --> 23:00.740 Then logic or operators are there and or not. 290 23:02.480 --> 23:10.610 Then special operators are there between in like is any all exist pivot set operators are their union 291 23:10.610 --> 23:12.560 union or intersect and accept. 292 23:20.360 --> 23:22.700 So these are the set operators. 293 23:24.640 --> 23:27.340 So now let's see one by one. 294 23:29.470 --> 23:33.040 Now to retrieve or fetch data from the table. 295 23:33.040 --> 23:37.390 What we are using we are using the select statement right. 296 23:38.620 --> 23:40.360 We are using the select statement. 297 23:40.540 --> 23:48.520 And we can by using the select star from table name what we are getting. 298 23:52.880 --> 23:55.550 We are getting all the rows and all the columns right. 299 23:55.910 --> 23:58.580 Display all the data from the EMP table. 300 23:59.180 --> 24:05.210 So by select star from EMP table we are getting all the rows and all the tables. 301 24:07.010 --> 24:11.270 So this is around sorry all the columns and all the rows. 302 24:11.960 --> 24:22.090 But now if I want to mention some specific column only then I can mention like this also EMP and salary. 303 24:22.090 --> 24:23.560 So this will give only me. 304 24:24.130 --> 24:25.660 Two columns are right. 305 24:28.180 --> 24:31.540 Now I think age is not the part of this table. 306 24:31.810 --> 24:35.500 So another column we can get it like this. 307 24:35.500 --> 24:36.400 Higher date. 308 24:38.120 --> 24:42.320 So this will give me a higher date. 309 24:43.160 --> 24:48.170 This may be very simple, but we will gradually we will move forward. 310 24:50.630 --> 24:55.190 Now suppose I want to filter some data from the table at that time. 311 24:55.190 --> 24:56.810 What condition I can use. 312 25:01.240 --> 25:03.730 The rare condition I can use, right? 313 25:04.360 --> 25:11.050 So it is used to get specific rows or rows from the table based on certain condition. 314 25:11.230 --> 25:15.910 Now what conditions we can use in the Where clause. 315 25:16.150 --> 25:20.230 So we can use conditions should be some expression. 316 25:22.270 --> 25:27.650 Some expression will be there also relationship which should result in true or false. 317 25:29.930 --> 25:33.740 Then for every single row of a table, condition will be evaluated. 318 25:34.310 --> 25:39.530 Now when you are mentioning the Where clause at that time, what will happen? 319 25:39.620 --> 25:41.810 Suppose let me write it. 320 25:41.810 --> 25:44.300 Select star from employee. 321 25:44.330 --> 25:44.900 Where? 322 25:47.000 --> 25:47.720 Where? 323 25:47.720 --> 25:47.740 Ban. 324 25:54.100 --> 25:54.670 DPT. 325 25:58.240 --> 25:59.440 Equal to 20. 326 25:59.650 --> 26:07.600 So now when you are specifying condition in the Where clause at that time, this particular condition 327 26:07.780 --> 26:11.350 will be evaluated for each of the row each of the row. 328 26:11.380 --> 26:15.260 So what it will do it will go to the first row first attempt. 329 26:15.590 --> 26:21.350 So now it will check whether DPT equal to ten, DPT equal to 20. 330 26:21.500 --> 26:23.990 So DPT equal to not 20. 331 26:24.020 --> 26:24.230 Right. 332 26:24.230 --> 26:26.420 So it will be false. 333 26:26.420 --> 26:29.990 So this condition is evaluated and it is false. 334 26:30.110 --> 26:31.940 So this row will not retrieve. 335 26:32.150 --> 26:39.850 Then it will go to the second row and it will evaluate the condition that DPT equal to 20. 336 26:41.140 --> 26:42.820 So now this is true right. 337 26:42.820 --> 26:46.660 So in this case this row will be evaluated. 338 26:47.020 --> 26:50.530 So again like this it will evaluate it for each and every row. 339 26:51.220 --> 26:52.450 And it will check. 340 26:52.450 --> 27:00.010 So over here all the 20 department will be retrieved only not other rows right. 341 27:04.550 --> 27:07.790 But if the condition is false, that row is not selected. 342 27:07.790 --> 27:08.330 Right? 343 27:10.370 --> 27:14.240 Now, this is one more example I have given. 344 27:16.580 --> 27:17.480 Okay. 345 27:27.700 --> 27:28.090 Um. 346 27:28.090 --> 27:28.450 Yeah. 347 27:28.450 --> 27:28.870 Yeah. 348 27:31.210 --> 27:32.470 I guess this is right. 349 27:32.950 --> 27:36.220 We will see that example also in few minutes. 350 27:38.410 --> 27:40.030 That we can call as a compound. 351 27:40.030 --> 27:49.600 Well where condition compound, in which case we can mention multiple conditions with different operators 352 27:49.600 --> 27:52.070 like and or like that. 353 27:55.100 --> 27:57.650 So now over what is the column? 354 27:57.650 --> 27:59.360 Actually I forget the column. 355 28:02.870 --> 28:05.090 Let me copy this data over here. 356 28:11.300 --> 28:13.160 How you can copy this result set. 357 28:13.160 --> 28:20.350 You have to do right click copy with headers and then you can paste it over here. 358 28:27.520 --> 28:34.360 Now let's see another condition where MP id equal to this one. 359 28:35.260 --> 28:40.110 So let me take it MP number right. 360 28:40.110 --> 28:43.560 So this is the exact column. 361 28:43.560 --> 28:50.430 So this will give me only one row because only one employee with MP number 7369. 362 28:50.430 --> 28:50.940 Right. 363 28:52.410 --> 28:55.890 Now let's see one more example. 364 28:56.850 --> 28:58.290 This is simple num. 365 28:58.770 --> 29:05.260 Now we have to check the detail of the employees earning more than 2500. 366 29:06.130 --> 29:08.860 So now this entire table set. 367 29:08.860 --> 29:09.910 Let me. 368 29:32.970 --> 29:33.150 Okay. 369 29:33.150 --> 29:34.950 Now, what is our question over here? 370 29:46.770 --> 29:50.070 Now, can anyone tell me actually, I. 371 29:53.260 --> 29:54.190 Moved in. 372 29:57.730 --> 30:00.910 Now, can you can anyone help me to write this query? 373 30:08.170 --> 30:08.710 Okay. 374 30:14.260 --> 30:16.590 Yeah, it is in front of you now. 375 30:19.290 --> 30:19.710 Yeah, yeah. 376 30:19.710 --> 30:21.600 You are able to see this drop down. 377 30:21.690 --> 30:22.320 Right, right. 378 30:22.350 --> 30:23.220 EMP number. 379 30:23.340 --> 30:24.030 Name. 380 30:24.330 --> 30:25.590 Job manager. 381 30:28.020 --> 30:28.440 Yeah. 382 30:28.440 --> 30:28.710 Yeah. 383 30:28.710 --> 30:29.460 Yes. 384 30:35.250 --> 30:35.700 Okay. 385 30:35.700 --> 30:36.000 Yes. 386 30:36.000 --> 30:36.540 Right. 387 30:39.610 --> 30:41.410 Let me show you the result. 388 30:41.980 --> 30:47.980 So now this all this employee salary are greater than or equal to 2500. 389 30:48.880 --> 30:54.520 But now someone told that, uh, well, how we can mention the few more conditions. 390 30:55.060 --> 31:02.830 So now, from this result set, I want the detail of department number equal to 20 also. 391 31:07.830 --> 31:16.590 Means I want okay what I want I want employee detail who is earning more than or equal to 10,500 an 392 31:16.590 --> 31:16.800 hour. 393 31:16.800 --> 31:18.030 Working on the department. 394 31:18.030 --> 31:19.320 Number 20 only. 395 31:27.640 --> 31:28.390 Yeah. 396 31:28.390 --> 31:29.350 Perfect. 397 31:34.570 --> 31:37.000 So now this is correct, right? 398 31:37.660 --> 31:48.670 But now what if I want one information whether the salary is greater than or equal to 10,500 or less 399 31:48.670 --> 31:50.560 than or equal to 2500. 400 31:50.920 --> 31:55.480 I want all the department who is 2020. 401 31:59.500 --> 32:01.300 You got my question right? 402 32:10.390 --> 32:10.780 Okay. 403 32:16.240 --> 32:17.230 now, now I want. 404 32:17.260 --> 32:18.490 Now what I want. 405 32:21.160 --> 32:22.090 Display. 406 32:24.070 --> 32:25.420 Please be on mute. 407 32:25.450 --> 32:38.020 Uh, this, uh, display the details of the employees is more than or equal to 2500. 408 32:38.020 --> 32:38.710 And. 409 32:41.400 --> 32:46.500 And also the details of the employee. 410 32:48.660 --> 33:05.590 Who are working on department number 20, whether they are earning more than or less than anything will 411 33:05.590 --> 33:06.520 be fine. 412 33:14.500 --> 33:15.880 Now, this is the question. 413 33:16.150 --> 33:18.850 Now, can you tell me how we can write this query? 414 33:31.230 --> 33:32.400 Yeah. 415 33:43.020 --> 33:43.620 Perfect. 416 33:44.340 --> 33:48.030 Now, this employees salary is less than 10,500. 417 33:48.060 --> 33:49.830 Still, it is showing, right? 418 33:50.790 --> 33:53.500 Because it is working on department number 20. 419 33:58.120 --> 34:03.010 In this 5000 is showing because the salary more than 2500. 420 34:03.010 --> 34:05.770 Even though he is working on 20. 421 34:06.400 --> 34:07.210 Sorry ten. 422 34:10.060 --> 34:12.520 This is called as compound where condition. 423 34:12.820 --> 34:15.220 It means multiple where condition right. 424 34:25.080 --> 34:26.130 No no no no. 425 34:26.220 --> 34:27.720 And we have already put over here. 426 34:27.720 --> 34:28.260 Right. 427 34:34.200 --> 34:36.240 And we have already put over here. 428 34:37.410 --> 34:42.010 It is not uh, run this both of the query at the same time. 429 34:49.630 --> 34:52.270 And check how many rows it is giving. 430 34:52.270 --> 34:56.710 Then how many rows it is giving ten and for row difference right. 431 35:04.920 --> 35:11.670 This is how you should know when to use and when to use, or you should be aware about it. 432 35:14.970 --> 35:15.660 You got it right. 433 35:15.660 --> 35:15.870 Why? 434 35:15.870 --> 35:16.110 Why? 435 35:16.110 --> 35:17.580 We have used the Or. 436 35:21.360 --> 35:22.290 Okay. 437 35:26.280 --> 35:34.330 Now display the employee details of those employee who joined after 2020. 438 35:35.800 --> 35:37.060 This is the table. 439 35:47.950 --> 35:49.390 We join after 2020. 440 35:49.420 --> 35:51.460 How many employee will show? 441 35:52.180 --> 35:55.740 It should show these two. 442 36:00.210 --> 36:01.410 Then? 443 36:13.830 --> 36:15.150 Then maybe last two. 444 36:19.370 --> 36:20.750 Now, how can we write the. 445 36:20.750 --> 36:23.510 We want this four row into our result set? 446 36:24.440 --> 36:26.090 How can we write this query? 447 36:38.420 --> 36:38.720 Where. 448 36:38.720 --> 36:40.400 Higher date. 449 36:40.400 --> 36:41.520 Greater than. 450 37:02.820 --> 37:04.170 Okay, perfect. 451 37:06.260 --> 37:06.950 One more. 452 37:06.950 --> 37:07.550 More way. 453 37:07.550 --> 37:08.660 It is possible. 454 37:11.420 --> 37:12.650 Can you tell me? 455 37:16.820 --> 37:19.220 We will see any way further that. 456 37:23.720 --> 37:25.700 We can write like. 457 37:28.280 --> 37:29.790 This is also one operator, right? 458 37:29.790 --> 37:30.330 Right. 459 37:30.930 --> 37:32.070 Now let's try. 460 37:33.630 --> 37:37.500 Oh, it is not giving okay. 461 37:37.500 --> 37:38.280 It will. 462 37:41.010 --> 37:41.490 Why? 463 37:41.490 --> 37:42.570 It is not giving. 464 37:48.000 --> 37:49.680 Yeah that is fine. 465 37:54.500 --> 37:55.430 No. 466 38:04.040 --> 38:04.820 No. 467 38:06.500 --> 38:07.160 Why? 468 38:07.160 --> 38:09.770 Why, uh, can you see this table? 469 38:16.010 --> 38:16.700 Yeah. 470 38:16.700 --> 38:17.600 Perfect. 471 38:18.210 --> 38:19.590 Now nothing is 2020. 472 38:19.590 --> 38:22.470 If I do 2021, then. 473 38:23.670 --> 38:27.150 Okay, let me mention it at the start. 474 38:32.910 --> 38:36.390 Still, it is not not giving that dimension. 475 38:42.050 --> 38:43.400 Okay, now it is giving. 476 38:46.640 --> 38:49.670 In 2021, exactly three employees has joined, right? 477 38:49.670 --> 38:51.740 One, two and three. 478 38:55.100 --> 39:00.110 So anyway, this way we will see like operator again in future. 479 39:00.290 --> 39:01.850 Now let's move ahead. 480 39:05.450 --> 39:07.740 Now this is also same easy thing, right? 481 39:07.770 --> 39:12.240 Display the employee details for join before 2020. 482 39:12.570 --> 39:17.400 So select star from employee where higher date less than 2020. 483 39:17.580 --> 39:20.130 So if I see this one. 484 39:23.610 --> 39:26.910 Then all this employee are joined before 2020 right. 485 39:27.480 --> 39:29.430 These four employees will not come. 486 39:37.370 --> 39:38.450 Now compound where? 487 39:38.450 --> 39:39.140 Condition. 488 39:39.140 --> 39:39.890 Let's see. 489 39:39.890 --> 39:41.600 Now compound where condition. 490 39:48.200 --> 39:53.270 So we can mention the compound where condition with the Or operator as well as end operator. 491 39:53.750 --> 40:00.750 Now this one, the first question will be our query how we can write this one. 492 40:00.750 --> 40:06.930 Display the details of the employee who are working as a clerk in earning more than 4000. 493 40:09.120 --> 40:12.450 Who are working as a clerk and earning more than 4000. 494 40:18.770 --> 40:20.090 Okay, let's write it. 495 40:20.120 --> 40:27.740 Select star from employee where job equal to clerk and. 496 40:30.080 --> 40:32.450 Salary greater than. 497 40:39.200 --> 40:40.040 Perfect. 498 40:40.430 --> 40:42.170 Now one more example. 499 40:42.170 --> 40:48.690 Display the details of the employee working as clerk or clerk and manager. 500 40:54.600 --> 40:56.610 Now how can I mention this one? 501 41:04.020 --> 41:04.860 Okay. 502 41:08.660 --> 41:09.710 Yeah. 503 41:11.720 --> 41:12.500 Just perfect. 504 41:12.500 --> 41:13.250 Perfect. 505 41:17.720 --> 41:17.900 Yeah. 506 41:17.900 --> 41:18.860 Either this or that. 507 41:18.860 --> 41:21.110 But what if I do mention over here and. 508 41:26.000 --> 41:26.660 Perfect. 509 41:26.660 --> 41:28.010 It will not satisfy it. 510 41:28.010 --> 41:30.050 It will won't give us any result. 511 41:33.630 --> 41:36.030 But now, one more thing also we can do. 512 41:36.030 --> 41:36.840 Can you? 513 41:36.840 --> 41:37.920 Anyone has idea. 514 41:41.070 --> 41:41.640 Yeah. 515 41:41.640 --> 41:42.450 Perfect. 516 41:48.540 --> 41:50.970 We can mention where job in. 517 41:58.880 --> 42:01.640 So this both query will give us the same result. 518 42:02.270 --> 42:06.830 So in SQL we can achieve one thing with multiple different ways right. 519 42:07.250 --> 42:09.140 That is the beauty of SQL. 520 42:09.140 --> 42:13.460 We can say now I want this job ID. 521 42:16.910 --> 42:19.410 Apart from clerk and manager then? 522 42:25.950 --> 42:26.400 Yeah. 523 42:26.400 --> 42:27.270 Perfect. 524 42:27.630 --> 42:29.790 Well, job not in. 525 42:33.750 --> 42:35.850 It will exclude the clerk and manager. 526 42:35.850 --> 42:36.450 Right. 527 42:39.990 --> 42:43.460 Now, let's understand this point. 528 42:47.780 --> 42:55.970 So now our operator and end operator, how it will work on the compound condition that we have to understand. 529 42:56.990 --> 42:59.390 So compound condition you understand. 530 42:59.390 --> 42:59.690 Right. 531 42:59.690 --> 43:01.130 This is the compound condition. 532 43:01.130 --> 43:04.430 This line is my compound condition. 533 43:04.940 --> 43:08.380 Now if this is one condition this is second condition. 534 43:08.380 --> 43:09.880 So condition one. 535 43:10.240 --> 43:11.470 Condition two. 536 43:11.500 --> 43:20.830 So if my condition one is false, and if my condition two is also false, then result will be false. 537 43:22.540 --> 43:24.040 Result will be false. 538 43:24.070 --> 43:25.360 You got it right. 539 43:25.600 --> 43:27.970 If there is no classes exist. 540 43:27.970 --> 43:30.460 If there is no manager is exist. 541 43:30.760 --> 43:33.290 In that case, both the condition are false. 542 43:33.320 --> 43:35.390 So in that case what? 543 43:35.390 --> 43:36.620 My query will return? 544 43:36.620 --> 43:37.730 Nothing, right? 545 43:39.860 --> 43:40.520 My query. 546 43:40.850 --> 43:42.260 That is why it is false. 547 43:42.260 --> 43:46.490 And in in the false scenario, data will be return nothing. 548 43:48.170 --> 43:50.480 Now let's consider the second row. 549 43:50.570 --> 43:53.660 If one condition is false, second condition is true. 550 43:54.530 --> 43:57.130 In that case, it will be true only, right? 551 43:57.310 --> 43:59.110 It will result some data. 552 44:03.730 --> 44:10.210 Now the reverse case also possible if my first condition is true and second condition is false. 553 44:10.690 --> 44:14.500 In that case also something will return, right? 554 44:14.500 --> 44:16.240 Some table will be written. 555 44:17.710 --> 44:19.390 Some rows will be written right. 556 44:22.700 --> 44:26.930 Now, if both the conditions are true, then also it will be true. 557 44:26.960 --> 44:31.340 Now can anyone tell me what will be in the case of end operator? 558 44:31.940 --> 44:33.650 This is the result set of or. 559 44:33.650 --> 44:34.400 Operator. 560 44:34.940 --> 44:38.960 Now what will be the result set of end operator? 561 44:47.080 --> 44:47.530 Okay. 562 44:47.530 --> 44:50.080 And over here it will be force over here. 563 44:55.180 --> 44:57.160 No, it will be false only. 564 44:58.990 --> 45:00.010 Now over here. 565 45:00.010 --> 45:01.480 It will be false only. 566 45:03.610 --> 45:12.920 And when both the conditions are true, then only it will be true whenever in the Or clause any of the 567 45:12.920 --> 45:15.050 conditions are true, it will be true. 568 45:19.100 --> 45:20.000 You got it right. 569 45:20.000 --> 45:22.190 This is very important thing. 570 45:23.750 --> 45:24.290 This will. 571 45:24.290 --> 45:27.410 Same thing will be apply in mathematics also. 572 45:27.410 --> 45:28.010 Right. 573 45:32.560 --> 45:34.180 See what is written over here. 574 45:34.180 --> 45:39.520 For output to be true, all the conditions have to be true in case of end operator. 575 45:39.970 --> 45:44.740 Even if even if single condition is false, output will be false. 576 45:51.940 --> 45:57.950 Now we have seen this one display the detail of the war working as clerk and earning more than 4000. 577 45:58.430 --> 46:03.530 This one also we have seen now over here what is mentioned? 578 46:05.660 --> 46:07.280 Display the employee details. 579 46:07.280 --> 46:15.440 Whose employee ID either 1000 or 100 or 1 zero 3 or 1 zero five. 580 46:15.590 --> 46:18.350 So we can write multiple or conditions, right? 581 46:18.350 --> 46:19.370 Not only one. 582 46:19.580 --> 46:21.730 We can write multiple or conditions. 583 46:21.730 --> 46:23.740 And let's see the result of this one. 584 46:25.690 --> 46:28.120 Okay MP number. 585 46:28.120 --> 46:28.660 Right. 586 46:41.950 --> 46:52.580 So only one employee satisfying this condition because 10103 and 105 there is no such employees are 587 46:52.580 --> 46:53.270 there right? 588 46:53.900 --> 46:56.060 With 103 and 105. 589 46:59.630 --> 47:00.470 Into the table. 590 47:00.470 --> 47:05.330 If you see this table, there is no employee of one zero 3 or 1 zero five. 591 47:08.500 --> 47:10.360 Now let's move ahead. 592 47:14.320 --> 47:15.010 Okay. 593 47:15.940 --> 47:16.690 Now. 594 47:18.760 --> 47:20.200 You have seen this query, right? 595 47:20.200 --> 47:21.430 Display employee details. 596 47:21.430 --> 47:25.810 Who is earning more than 5000 and less than 10,000. 597 47:27.490 --> 47:36.770 So we want let me change the condition 1000 to 3000 because we have data like that. 598 47:44.660 --> 47:53.570 So this will give me those employees who are earning more than 1000 and less than less than 3000. 599 47:53.660 --> 47:55.610 But now one more way is there. 600 47:55.640 --> 47:58.060 Can anyone tell me what is the another way? 601 48:04.900 --> 48:05.500 Ah, yes. 602 48:05.500 --> 48:06.820 Right now. 603 48:10.210 --> 48:10.540 Where? 604 48:10.540 --> 48:11.230 Salary. 605 48:14.140 --> 48:15.190 Between. 606 48:18.340 --> 48:24.170 So when you write the between operator let me do one thing. 607 48:28.160 --> 48:30.770 Can anyone tell me whether both are same or not? 608 48:41.510 --> 48:43.310 Okay, let's try it. 609 48:45.070 --> 48:45.460 Okay. 610 48:45.460 --> 48:45.700 Yes. 611 48:45.700 --> 48:46.000 Right. 612 48:46.000 --> 48:50.770 It should be 1000 to 3000 because in the between operator. 613 48:50.800 --> 49:01.120 Remember one thing lowest value should be given first whether you are using date, date, operator or 614 49:01.120 --> 49:03.940 sorry date column or anything. 615 49:04.270 --> 49:10.040 Always remember lowest value should be given first and largest value should be given second. 616 49:10.670 --> 49:13.670 So these both are not the same one thing, right? 617 49:14.000 --> 49:18.230 Now can anyone tell me both these queries are same? 618 49:27.770 --> 49:29.180 Anyone else? 619 49:34.330 --> 49:34.570 It. 620 49:41.920 --> 49:43.150 Yeah. 621 49:44.770 --> 49:45.520 Yeah. 622 49:45.520 --> 49:46.810 Perfect. 623 49:48.610 --> 49:49.000 Yes. 624 49:49.000 --> 49:49.870 Yes is perfect. 625 49:49.870 --> 49:51.160 But if I do over here. 626 49:51.160 --> 49:51.970 Equal to. 627 49:54.640 --> 49:55.480 Greater than. 628 49:56.020 --> 49:56.500 Greater than. 629 49:56.500 --> 49:57.280 Equal less than. 630 49:57.290 --> 49:58.070 now. 631 49:58.250 --> 49:59.390 Same right. 632 50:02.480 --> 50:03.050 Let's see. 633 50:07.430 --> 50:08.210 1313. 634 50:08.210 --> 50:09.890 Both are giving same number of record. 635 50:11.000 --> 50:12.140 No, no that is fine. 636 50:12.140 --> 50:13.520 Semicolon is fine. 637 50:13.520 --> 50:17.510 Semicolon indicates now this statement is closed over. 638 50:19.040 --> 50:25.210 Semicolon indicates this statement is over and another statement will start after this. 639 50:28.510 --> 50:29.890 Then also it will be fine. 640 50:30.010 --> 50:34.900 Nothing matters over here in this case. 641 50:39.820 --> 50:41.110 Got it right. 642 50:43.930 --> 50:46.590 Okay, now, now over here in the higher date. 643 50:46.590 --> 50:47.760 Also I have used. 644 50:51.390 --> 50:54.810 Display the detail of the employee who joined in 2020. 645 50:57.060 --> 50:59.160 So now this thing also you can do. 646 50:59.160 --> 50:59.730 Right. 647 51:01.170 --> 51:01.590 Great. 648 51:01.590 --> 51:03.090 Greater than equal to this one. 649 51:03.090 --> 51:03.720 And. 650 51:05.910 --> 51:12.970 Now between also you can write over here in this scenario also you can right between higher date. 651 51:19.270 --> 51:20.830 Between this date. 652 51:24.250 --> 51:25.450 And this date. 653 51:25.810 --> 51:32.260 Now both of my query will give the same result okay I think okay. 654 51:32.740 --> 51:34.620 Let me try it. 655 51:35.460 --> 51:36.660 2024. 656 51:40.080 --> 51:42.870 Because in 2020, no employees are joined, right? 657 51:43.110 --> 51:45.210 So that is why it is not giving me result. 658 51:45.240 --> 51:47.640 Now it is giving me correct result. 659 51:47.640 --> 51:48.210 Right? 660 51:53.820 --> 51:55.200 Now. 661 52:00.520 --> 52:04.150 Now this is also very simple one in operator. 662 52:04.150 --> 52:11.890 So what we have done over here, we have used previously 100 103 and 105 with our condition. 663 52:11.890 --> 52:18.790 But same thing we can use with the in operator like this select star from employee where employee ID 664 52:18.790 --> 52:23.070 in 100103105. 665 52:23.280 --> 52:24.450 Same like this. 666 52:24.450 --> 52:25.230 Over here. 667 52:25.800 --> 52:26.310 Where? 668 52:26.310 --> 52:28.500 Job in clerk and manager. 669 52:29.070 --> 52:30.720 I have shown you also this one. 670 52:30.720 --> 52:31.020 Where? 671 52:31.020 --> 52:33.630 Clerk not in clerk and manager. 672 52:33.630 --> 52:34.800 So it will not show you. 673 52:34.800 --> 52:36.120 Clerk in manager's detail. 674 52:36.120 --> 52:36.660 Right. 675 52:39.390 --> 52:41.760 Then we have seen between operator as well. 676 52:44.040 --> 52:46.050 Salary between 5000. 677 53:24.570 --> 53:27.330 Means no, I am not. 678 53:57.460 --> 53:58.780 Let me try this one. 679 54:01.380 --> 54:01.620 Yeah. 680 54:01.620 --> 54:03.270 We have seen already this one. 681 54:03.270 --> 54:03.480 Right. 682 54:03.480 --> 54:05.340 Multiple where condition we can. 683 54:05.340 --> 54:06.000 Sorry. 684 54:06.000 --> 54:08.490 Where will be written only one time. 685 54:08.760 --> 54:10.500 So see over here. 686 54:15.660 --> 54:16.170 Okay. 687 54:16.170 --> 54:16.830 Not between. 688 54:16.830 --> 54:17.370 Right. 689 54:17.370 --> 54:20.250 Let me write it between only. 690 54:29.500 --> 54:31.270 So now see this one? 691 54:31.270 --> 54:35.500 Even though this is not satisfying our condition. 692 54:35.500 --> 54:36.040 Right? 693 54:36.640 --> 54:39.910 These rows are not satisfying our first condition. 694 54:40.210 --> 54:44.140 First condition means it is not between 2020 to 2024. 695 54:44.380 --> 54:45.490 Write higher date. 696 54:46.810 --> 54:47.950 But still it is showing. 697 54:47.980 --> 54:48.520 Why? 698 54:48.730 --> 54:51.460 Because one more condition I have written. 699 54:54.070 --> 54:55.660 Department is equal to 20. 700 54:55.660 --> 54:58.390 So these four rows are department 20. 701 54:58.660 --> 55:06.310 That is why it is showing in other rows are showing because of it is satisfying first condition. 702 55:08.890 --> 55:10.930 It is satisfying this condition. 703 55:16.000 --> 55:18.850 So we can mention as much as possible. 704 55:19.390 --> 55:19.990 Condition. 705 55:19.990 --> 55:23.920 But it will retrieve whatever column you are mentioning over here. 706 55:24.400 --> 55:26.170 Select in select clause. 707 55:30.910 --> 55:37.470 If you mention over here three column then it will show you only three column like MP number, comma 708 55:37.470 --> 55:38.250 e name. 709 55:43.080 --> 55:43.380 Comma. 710 55:43.380 --> 55:43.860 Salary. 711 55:44.610 --> 55:51.150 So now for this result set nine rows are I think nine rows are there. 712 55:51.150 --> 55:51.690 Right. 713 55:51.690 --> 55:54.690 So for this nine rows it will show you only three columns. 714 55:58.590 --> 56:00.670 In which condition it is checking. 715 56:00.670 --> 56:02.920 It is checking two conditions. 716 56:02.920 --> 56:06.490 One is the higher rate and another one is department. 717 56:06.490 --> 56:09.040 But now what if I mention over here and. 718 56:12.370 --> 56:17.470 I am not sure whether any row is satisfying this condition or not. 719 56:22.630 --> 56:23.020 Okay. 720 56:23.020 --> 56:24.270 This row is satisfying. 721 56:24.300 --> 56:26.820 Let me mention over here how hard it is. 722 56:26.820 --> 56:27.270 Well. 723 56:35.310 --> 56:38.310 See, now both the conditions are satisfied, right? 724 56:39.360 --> 56:41.730 That is why it is giving us only two rows. 725 56:47.760 --> 56:48.060 Okay. 726 56:48.060 --> 56:49.420 We will see from here. 727 56:49.420 --> 56:51.280 I think this is the same thing. 728 56:51.280 --> 56:53.350 Clark manager earning between. 729 56:59.380 --> 56:59.770 Okay. 730 56:59.770 --> 57:01.360 We will see from here tomorrow. 731 57:01.360 --> 57:04.600 Like operator in detail. 732 57:10.540 --> 57:13.090 Now let me see any doubt.