1
00:00:00,300 --> 00:00:07,230
Hopefully, you would have already figured out how to delete the user data from here, but if not,

2
00:00:07,260 --> 00:00:09,100
it's very, very simple and straightforward.

3
00:00:09,130 --> 00:00:14,190
Guys, I mean, the way which I can do the delete operation is I mean, I can do it in many different

4
00:00:14,190 --> 00:00:14,520
ways.

5
00:00:14,670 --> 00:00:22,920
But the easiest way is you can directly parse the export of that particular user and then you can delete

6
00:00:22,920 --> 00:00:23,070
it.

7
00:00:23,340 --> 00:00:27,700
Does that the XPath should be even more dynamic than what it is at the moment.

8
00:00:28,080 --> 00:00:33,190
So, for example, if I want to delete this user, its title to reverse this guy over here.

9
00:00:33,510 --> 00:00:35,130
So this is the test user we have.

10
00:00:35,250 --> 00:00:42,090
And if I want to perform a delete operation, all I can do is I can just do a download a daughter and

11
00:00:42,090 --> 00:00:45,680
then I can search for that as as delete.

12
00:00:45,710 --> 00:00:50,540
You can see that it is not going to show us exactly which you are talking about.

13
00:00:50,850 --> 00:00:58,200
And if I just do a dollar X off the double slash of TRD of text, it is not going to work.

14
00:00:58,510 --> 00:01:05,130
We somehow need to put in normalize space to make that operation working as expected.

15
00:01:05,130 --> 00:01:08,210
So you can see that this is the normalized space which I'm talking about.

16
00:01:08,610 --> 00:01:18,780
So I can just go over here and then instead of DTD, I can just paste this guy like normal space and

17
00:01:18,780 --> 00:01:20,580
you can see that I get the DVD's for that.

18
00:01:20,820 --> 00:01:24,350
But the problem is it's going to give us all the DVDs like all these.

19
00:01:24,360 --> 00:01:25,830
That coming up over here.

20
00:01:26,130 --> 00:01:26,550
Right.

21
00:01:26,820 --> 00:01:30,890
But I need to delete exactly for this particular user, that test user.

22
00:01:31,290 --> 00:01:38,280
So in order to do the exact delete operation for that user, we can do it either by identifying that

23
00:01:38,280 --> 00:01:41,680
particular user, the test user, and then perform the operation.

24
00:01:41,700 --> 00:01:46,500
So, uh, so what I really mean in here is I can just do a.

25
00:01:48,820 --> 00:01:56,380
Operation, something like this, as you can see, what I did is to normalize space dot just auto user

26
00:01:56,380 --> 00:02:03,880
this guy and go to the patent office role so that I can get the role, this role, and then do a normalized

27
00:02:03,880 --> 00:02:06,250
space and then perform a delete operation.

28
00:02:06,260 --> 00:02:10,720
So you can see that I find exactly that same delete operation over there.

29
00:02:11,200 --> 00:02:17,500
So this way I could be able to perform a delicate operation instead of having this operation, which

30
00:02:17,500 --> 00:02:19,360
is not going to work basically.

31
00:02:19,640 --> 00:02:29,020
So I can just replace this to this guy and probably I'm going to use a string interpolation this time.

32
00:02:29,470 --> 00:02:32,560
So I'm just going to use like that.

33
00:02:32,740 --> 00:02:37,240
And instead of the disk user, which I time passing hardcoded because tomorrow the data might change

34
00:02:37,240 --> 00:02:40,570
and we're not going to use the same test user, which is also not correct.

35
00:02:40,870 --> 00:02:48,910
So I'm just going to use this guy and I'm going to say DataDot user dot name something like this and

36
00:02:48,910 --> 00:02:50,450
then perform a delicate operation.

37
00:02:50,470 --> 00:02:55,480
So this way it is going to perform a delicate operation for me, which is going to be really, really

38
00:02:55,480 --> 00:02:56,420
cool as well.

39
00:02:56,440 --> 00:02:58,030
So I'm just going to save this.

40
00:02:58,330 --> 00:03:05,680
And now if I try to run that, but before running it, I'm just going to really delete this user so

41
00:03:05,680 --> 00:03:07,300
that we don't really have this users.

42
00:03:07,460 --> 00:03:11,620
And this other user is also unnecessarily making the data more rubbish.

43
00:03:12,010 --> 00:03:15,550
So I'm just going to delete it now and I'm going to save this.

44
00:03:15,550 --> 00:03:22,390
And if I try to run this test, you could see that the test should run creating a user and you should

45
00:03:22,390 --> 00:03:23,710
also delete the user.

46
00:03:24,420 --> 00:03:27,610
You see that it's performing a delicate operation as well, which is quite good.

47
00:03:27,910 --> 00:03:32,430
So this may be good able to handle the delete operation from a table dynamically.

48
00:03:33,070 --> 00:03:40,810
There is another question students ask me, like, how can I grab all the table rose and table columns

49
00:03:40,810 --> 00:03:46,660
and it's data and store it in a collection or something like that, or maybe even export to a John file

50
00:03:46,660 --> 00:03:47,240
if I want to.

51
00:03:47,260 --> 00:03:49,050
I mean, you can do anything again.

52
00:03:49,330 --> 00:03:52,000
Imagination is the limit for doing everything.

53
00:03:52,150 --> 00:03:56,800
But if you want to really do that, you could also do that as well.

54
00:03:57,070 --> 00:03:58,650
We can talk about that in our next video.

55
00:03:58,660 --> 00:04:01,740
I mean, it's also one of the most simplest thing that you can do.

56
00:04:02,740 --> 00:04:05,110
Just give it a shot by yourself if you're able to do that.

57
00:04:05,110 --> 00:04:08,410
If you couldn't, the solution is already dead in our next lecture.