WEBVTT

00:00.520 --> 00:01.160
High.

00:01.470 --> 00:08.270
So we just went through the entire chapter and the last session.

00:08.280 --> 00:12.140
So all we had done that in my.

00:12.240 --> 00:13.340
So if you.

00:13.500 --> 00:21.220
So we started that out by Chang'e we had done things like creating a chat where one person sends and

00:21.240 --> 00:22.880
calls to everybody else.

00:22.920 --> 00:23.630
Right.

00:23.700 --> 00:36.060
So in this particular chapter we also saw the benefits of networking and we saw how networking is used

00:36.560 --> 00:41.070
in things much more than we could ever think about.

00:41.250 --> 00:47.880
So basically where a client can talk where multiple clients can talk for hours and using the chat up

00:47.930 --> 00:52.620
we did stuff like one client talks or multiple clients.

00:52.620 --> 00:53.230
Right.

00:53.280 --> 01:00.530
So as of now we of course these are a few things that we just did.

01:00.930 --> 01:07.500
We learned about multi-threading we learned about networking and of course we created the chatter of

01:07.500 --> 01:10.330
the chatter right now.

01:10.740 --> 01:21.570
Something else that we can think about or which we can concentrate upon is is things like we would we

01:21.570 --> 01:31.900
would want to we would want to understand more in detail something called as databases handling databases.

01:32.010 --> 01:41.210
So why databases are required for for a particular program or why is database so very important.

01:41.220 --> 01:44.740
So we have to create a package out here let's call it databases.

01:44.970 --> 01:50.030
And why is this very important for us.

01:50.040 --> 01:56.100
So let's think about it and let's go go much more in detail.

01:56.220 --> 01:56.780
OK.

01:57.060 --> 02:00.690
Now a database is nothing but where data is stored.

02:00.780 --> 02:01.290
Right.

02:01.320 --> 02:04.540
So if you have a look at chat apps right.

02:04.710 --> 02:08.000
Or in this particular application we had a client.

02:08.070 --> 02:09.130
So this is the client.

02:09.150 --> 02:11.340
And we also have the server.

02:11.340 --> 02:18.240
So the server what was what was doing was it was just basically whenever a client was run.

02:18.240 --> 02:25.320
So if I ran the server if you remember whenever I ran the server the server was running up and running

02:25.380 --> 02:27.390
and client and I ran the client.

02:27.380 --> 02:33.870
Then I said when I run the client and said ABC OK and all.

02:34.040 --> 02:36.610
And I ran another client.

02:36.680 --> 02:39.740
And let's say it was X Y Z.

02:40.070 --> 02:45.210
And now let me see another client let me say it was.

02:45.650 --> 02:49.760
Now you are so there were three lines.

02:49.850 --> 02:54.410
Each of them were connected and I got a connection from client to that address this that address this

02:54.410 --> 02:55.310
or that or this.

02:55.490 --> 02:56.020
Right.

02:56.030 --> 02:57.510
So I have stored.

02:57.560 --> 03:04.550
Now if I say hi from any one of them it goes to all the others at ABC right now.

03:04.550 --> 03:08.760
Now comes the question there will be a thousand clients in the world right.

03:09.140 --> 03:16.730
I could have stored I've stored all their details each client details or their connection and their

03:16.730 --> 03:21.800
name I have stored it in in this particular client's dictionary.

03:21.860 --> 03:29.270
But what if what if I had to store much more details about about each client.

03:29.270 --> 03:35.580
All right let's say I want to store much more details about each line.

03:35.750 --> 03:47.840
Let's say for example I wanted to store the client's name is his address is his Gnome's something like

03:47.840 --> 03:53.640
his phone number his email id I want to sort his email id at least I want his email ID to be stored

03:54.100 --> 04:01.430
and and then I would one along with his email id I wanted his date of birth to be stored.

04:01.520 --> 04:06.740
So these are things that you know every client every client's data needs to be stored.

04:06.740 --> 04:12.830
So now making a connection and storing the connection for each client in a dictionary is not enough

04:12.830 --> 04:18.370
because in a dictionary you can just have maximum a name and connection.

04:18.450 --> 04:22.020
That's it to just Hoopa just do arguments right.

04:22.070 --> 04:26.950
Name calling connection but you cannot have something more than that.

04:26.960 --> 04:34.650
Like for example it's you can have you can have corresponding to a name his role or his Chye his his

04:34.760 --> 04:35.880
entire history.

04:36.020 --> 04:36.950
You won't be able to.

04:37.160 --> 04:46.400
So it's best to either you know get things into files or either do some kind of file you know do some

04:46.400 --> 04:55.250
some kind of management of files or rather store them in databases so I could have stored in files but

04:55.290 --> 05:02.300
of files storing them in files and accessing them and files are a bit tedious of course because they're

05:02.300 --> 05:08.300
going to be stored statements and you know how to debug these statements how to create you know how

05:08.300 --> 05:11.230
to cut across the strings.

05:11.270 --> 05:16.820
It's very you know it's not that great but what if you have something like a spreadsheet where all the

05:16.820 --> 05:19.870
data was there in spreadsheets or something like that.

05:19.910 --> 05:25.190
So maybe you could have used a spreadsheet for that for that matter or see you file an excel file or

05:25.190 --> 05:28.930
something like that where we could have done that and then this is using panderers.

05:28.940 --> 05:36.710
But then what if you had to do it with if you had to do it with basic bited courting then in that case

05:36.770 --> 05:43.790
let's say for example more stuff the companies most of the applications most of them deal with deal

05:43.790 --> 05:52.010
extensively currently with database Hanzo So we need to get databases in detail and try to figure out

05:52.010 --> 05:57.740
how things work and how our database is related to each other and how they're going to go ahead and

05:57.740 --> 05:58.710
stuff like that.

05:59.030 --> 06:06.650
So we go ahead with that and and as we do it let's understand more in detail exactly how things happen

06:06.650 --> 06:09.060
and how things do not happen and stuff like that.

06:09.320 --> 06:09.790
OK.

06:09.930 --> 06:18.290
So indeed Hobbes's So one of the database that I'm going to deal with specifically currently is the

06:18.380 --> 06:24.540
escrow database or that's really like to wish short of the database.

06:24.650 --> 06:27.950
I might deal with the allotted a visa so the next sessions.

06:27.950 --> 06:35.030
But for now we're going to deal with deescalated visas where we're going to learn how to how data is

06:35.030 --> 06:40.280
stored and escalate databases and how they can be accessed using Python code and how Python code can

06:40.670 --> 06:41.390
store stuff.

06:41.390 --> 06:45.860
So we're going to use we are going to of course develop the same application a little more.

06:45.860 --> 06:51.470
That is a chat app we're going to Delap this application a bit more by storing a lot of plain details

06:51.770 --> 06:52.350
in data.

06:52.360 --> 06:56.840
So that's my long term long term goal for this particular session.

06:56.870 --> 07:05.130
But for now let's let's close all let's terminate all the connections as of now right now and let's

07:05.130 --> 07:06.420
start with databases.

07:06.560 --> 07:12.530
But for now let's see how things work out with the escalate and what exactly they escalate and what

07:12.530 --> 07:13.270
is.

07:13.490 --> 07:20.460
How do I create database in that particular fashion so you can just right now open into an icon prompt

07:22.400 --> 07:26.720
open of an icon a prompt and when you open up Anaconda prompt if you want to create a database Let's

07:26.720 --> 07:28.230
say I want to create a database.

07:28.230 --> 07:32.040
Let's see escalatory is the one we just used escalatory spaces.

07:32.240 --> 07:33.560
I want a real database.

07:33.560 --> 07:36.050
Let me call the database name company.

07:36.190 --> 07:36.490
OK.

07:36.490 --> 07:42.850
Company dot DP So basically dot tv in the shows that it is a database that I'm creating.

07:42.860 --> 07:45.140
So escalatory company daddy.

07:45.240 --> 07:53.870
So all when I am in a particular database that is when I'm in companied on the over here I need to create

07:53.870 --> 07:58.070
some tables inside companied IDBI to create something like that.

07:58.070 --> 08:01.720
So let me say I'm going to create a table that we call it does imply.
