1
00:00:00,720 --> 00:00:04,560
Hello and thank you for signing up to this course.

2
00:00:04,560 --> 00:00:11,660
This video will introduce you to some guidelines that you may want to follow.

3
00:00:11,670 --> 00:00:14,420
Weigh in right in rescue her query's.

4
00:00:14,510 --> 00:00:16,770
They are only guidelines.

5
00:00:16,770 --> 00:00:20,910
They are not set in stone is just too great.

6
00:00:21,150 --> 00:00:21,490
Right.

7
00:00:21,490 --> 00:00:30,450
We begin with the obscure statements insecure statements are not case sensitive health cure Simmons

8
00:00:30,460 --> 00:00:34,780
men's camby on one or more on line.

9
00:00:35,280 --> 00:00:41,730
Key words can not be a private or split across lines.

10
00:00:42,000 --> 00:00:47,500
So is it good practice to police Klaus on a separate line.

11
00:00:47,910 --> 00:00:52,720
Always end your statements with a semicolon.

12
00:00:54,990 --> 00:01:01,260
Indent your code wherever possible to make it easy to read.

13
00:01:01,590 --> 00:01:05,690
Use upper case for key words.

14
00:01:05,970 --> 00:01:15,570
Although as the holiday table names clomps in lower case you can use upper Keys for the key words and

15
00:01:15,570 --> 00:01:20,710
then things like table names some column names use lowercase.

16
00:01:20,820 --> 00:01:25,470
I personally tend to use upper case with everything.

17
00:01:25,470 --> 00:01:27,800
That means your preference of mine.

18
00:01:27,840 --> 00:01:31,690
Again this is just guidelines so you don't have to follow it.

19
00:01:31,710 --> 00:01:39,520
It's just a guideline to use upper case for keywords and then for table names a column name to use lowercase

20
00:01:40,350 --> 00:01:46,570
Eskew a statesmen's also known as query or script.

21
00:01:47,640 --> 00:01:54,990
Key word usually refers to individual escudo element for example.

22
00:01:55,020 --> 00:02:08,490
Select and from a no less keywords som database systems like horror or Microsoft's obscure server so

23
00:02:08,700 --> 00:02:13,240
have their own version of the obscure language.

24
00:02:13,470 --> 00:02:21,720
However they all have to perform setting functions in the same way and the function they perform in

25
00:02:21,720 --> 00:02:24,230
the same way is no house.

26
00:02:24,250 --> 00:02:27,720
Crowd C R U.

27
00:02:27,840 --> 00:02:40,290
D stands for create reeg of date and delete all support these functions in this same way.

28
00:02:40,480 --> 00:02:50,560
So all databases use select or date delete set home where these qualifiers are used.

29
00:02:50,580 --> 00:02:54,860
Or database systems in this same way.

30
00:02:55,200 --> 00:03:02,670
So these guidelines are just guidelines so you can follow them if you wish but they are just guidelines

31
00:03:02,670 --> 00:03:07,280
to help you write better rescuer queries.

32
00:03:08,010 --> 00:03:10,590
So thank you for watching this video.

33
00:03:10,620 --> 00:03:16,160
I just Kavos some of the some few guidelines that you may want to follow.

34
00:03:16,190 --> 00:03:20,110
You write obscure queries they are on the guidelines.

35
00:03:20,140 --> 00:03:23,850
They're not set in stone but I just saw it in their mouth.

36
00:03:23,850 --> 00:03:25,790
In case you want to use them.

37
00:03:26,010 --> 00:03:28,060
Thank you and bye for now.
