シャドーイング練習: Database Normalisation: Third Normal Form - 動画で英語スピーキングを学ぶ
レッスンを作成中...
1
Thank you.
2
This video is about database normalisation.
3
specifically normalising a database to a third normal form.
4
It follows on from the video about second normal form by working through the same example.
5
to qualify for third normal form in technical terms.
6
The data must already be in second normal form and a relation has no transitive functional dependencies on the primary key.
7
To put that more simply, the data must be in second normal form, and there is no other non -key attribute that you'd need to change in the table
8
if you change the non -key attribute.
9
Let's continue with our example.
10
To get these tables into third normal form, they must already be in second normal form.
11
Which they are.
12
Now you need to ensure that there are no transitive functional dependencies.
13
Well, actually in this case there aren't any, so these tables are already in third normal form as well.
14
But what's meant by a transitive functional dependency?
15
And how can you spot one?
16
Let's start by reviewing the term functional dependency.
17
In the students table, The first name is functionally dependent on the ID.
18
The ID is called the determinant, and the first name is called the dependent.
19
This is normally written like this.
20
Another way of saying it is that there is exactly one first name for any given instance of a student.
21
In the same way, last name is functionally dependent on ID, and so is marital status.
22
In the student course table there's a composite primary key which the grade is functionally dependent on.
23
It can be written like this.
24
You could also say that the course title in the student course table is functionally dependent on the composite primary key.
25
but because the course title is a subset of the composite key It's known as a trivial functional dependency.
26
It's OK to have functional dependencies in a table in order for it to be in third normal form.
27
In fact, it's absolutely necessary.
28
Every non -key attribute of a table must be fully functionally dependent on the primary key.
29
If it was partially dependent, the table wouldn't even be in second normal form.
30
So what's a transient functional dependency?
31
These are not allowed in third normal form.
32
Let's add some more data to the courses table to help make this clear.
33
The course title is still the primary key of the courses table.
34
It's unique for each course, it certainly belongs here.
35
As an aside, if there were two courses with the same course title, perhaps a computer science A level and a computer science diploma.
36
then you'd have to rethink the primary key, perhaps by giving each course a unique code.
37
But let's proceed on the basis that each course title will always be unique.
38
The fee and the qualification are both attributes of the course title.
39
They're functionally dependent on the primary key, so they belong here.
40
but the teacher ID and the teacher name columns seem a little out of place.
41
Each course is always taught by the same teacher, according to this data at least.
42
So you'd be forgiven for allowing them into this table in the first place.
43
Teacher ID is an attribute of a course, and it's functionally dependent on the primary key.
44
Teacher name is also an attribute of a course, and it too depends on the primary key.
45
There are no partial dependencies on the primary key here, so the table is indeed in second -normal form.
46
But there's a potential problem.
47
If you decide to change the teacher for a course, then you have to change both the teacher ID and the teacher name.
48
They are functionally dependent on each other.
49
This is not ideal because as you know, editing mistakes can lead to inconsistencies in the data.
50
If you change one of the course titles, it becomes a different course.
51
So again, you need to change the teacher ID and the teacher name.
52
To put this in technical jargon, the teacher ID is functionally dependent on the course title,
53
and the teacher name is functionally dependent on the teacher ID.
54
So there's a transitive dependency between the teacher name and the course title.
55
Something depends on something which depends on something else.
56
It's also true to say that the teacher name is functionally dependent on the course title, and that the teacher ID is functionally dependent on the teacher name.
57
So there's a transitive dependency between the teacher ID and the course title.
58
It's just another way of looking at these particular data.
59
whichever way you look at them, there are transitive functional dependencies here.
60
So the courses table violates third normal form.
61
This is how to solve the problem.
62
You need a separate teacher's table.
63
The teacher column in the courses table establishes the relationship with this new table.
64
None of these tables contain transitive functional dependencies.
65
the database is definitely in third normal form.
66
Another example of a transitive functional dependency would be
67
if the student course table contained an exam mark as well as the grade.
68
The grade is derived from the mark.
69
Now arguably you shouldn't store any attribute in the database if you can calculate it from something else.
70
Nevertheless, let's suppose you had good reason to store both the exam mark and the grade in this table.
71
If you change the value of the primary key for one of these records, it's a different student course combination.
72
So you need to change the exam mark and the grade to match.
73
The mark is functionally dependent on the primary key and the grade is functionally dependent on the mark.
74
There's a transitive functional dependency between the grade and the primary key Strictly speaking,
75
in order for this version of the table to be in third normal form, The mark and the grade belong in a table of their own, perhaps a table called results.
76
Let's stick with just the grade in this database.
77
Now take a look at this version of the Students table.
78
A purist might tell you that if you were storing postal addresses in the students' table, then these should be moved into another table.
79
Every part of the address is functionally dependent on the primary key.
80
but there are some transitive functional dependencies here.
81
If a student emigrates to a new country, then they'd necessarily moved to a new town and a new street address.
82
But you have to ask yourself if breaking up this table is actually practical.
83
For a start, addresses often have missing information.
84
But even if your data are complete, decompose them too much and they start to become unmanageable.
85
To get into third normal form, there are some simple clues you can look out for.
86
Are there any items that are obviously categories?
87
Is there anything that looks like an identifier?
88
Is there any more duplication of data?
89
But be careful with this.
90
Every student has a gender, but it doesn't really make sense to put genders in a separate table.
91
If you'd started with a flat file containing all of these data in the first place,
92
You may well have come up with this four -table structure straight away.
93
With experience, you'll eventually find you can normalise a database directly to third normal form or near enough,
94
just by looking at the data and applying a little common sense.
95
In summary, To be in third normal form,
96
The data must already be in second normal form and a relation has no transitive functional dependencies on the primary key.
97
or put more simply the data must already be in second normal form
98
and there is no other non -key attribute
99
that you would need to change in the table if you change to non -key attribute.
✨ おすすめ動画
C13
53 文
System Design Was HARD - Until You Knew the Trade-Offs
Business EnglishUniversity StudentsWorking Adults
C11
72 文
Overview of Fluid and Electrolyte Physiology (Fluid Compartment)
University StudentsWorking Adults
C13
28 文
0925.2 financial statements and ratios
Business EnglishUniversity StudentsWorking Adults
C11
537 文
Understand Microsoft Entra ID | AZ-104 | Episode 2
Business EnglishUniversity StudentsWorking Adults
C12
172 文
DRY Often Makes Your Code Worse
Business EnglishUniversity StudentsWorking Adults
C177 文
1 7 What is Information
University StudentsWorking Adults
C11
22 文
Introduction To Networking - Different Types Of Networks | Networking Fundamentals Part 2 (revised)
Business EnglishUniversity StudentsWorking Adults
C12
119 文
How to Write Test Cases for Manual Testing?
Business EnglishUniversity StudentsWorking Adults
C11
43 文
What is an Organization? - the Nature of Organizations
Business EnglishUniversity StudentsWorking Adults
C1158 文
7 Cấp Độ Toán Học: Bạn Đang Ở Đâu?
Business EnglishUniversity StudentsWorking Adults
C11
158 文
OWASP Top 10 Explained
Business EnglishUniversity StudentsWorking Adults
C11
132 文
Video
Business EnglishUniversity StudentsWorking Adults
なぜこのビデオで話す練習をするべきなのか？
このビデオは、データベースの正規化、特に第三正規形についての内容です。英語を学ぶ際、このビデオで取り上げられている専門的な語彙や概念を使って話す練習をすることにより、技術的なトピックに関する表現力を向上させることができます。特にIELTS スピーキング対策の一環としてこうしたトピックを活用することで、面接における専門用語や論理的な表現を強化し、自信を持って話す力を育成できます。また、英語シャドーイングを用いることで、発音や語調も改善できます。
文法と表現を文脈で分析
ビデオ内で使用されているいくつかの重要な文法構造や表現を以下に示します。
- 機能的依存関係: 「IDはファーストネームに機能的に依存している」という表現が繰り返され、原因と結果の関係を明確にしています。このような文の構造は、技術的な説明で非常に重要です。
- 部分依存: 「もし部分依存だった場合、テーブルは第二正規形にもなりません」というフレーズは、条件に基づく文構造を使用しています。このような条件文は、英語の運用能力を向上させるのに役立ちます。
- 無関係な属性: 「教師IDと教師名のカラムは少し場違いに見える」といった表現は、洞察を示すための巧妙な比較的表現を含んでいます。
一般的な発音の落とし穴
ビデオの中で注意すべき発音のトラップがいくつかあります。例えば、「機能的依存関係」という表現は、英語での発音が難しい場合があります。特に、「ID」と「ファーストネーム」の発音は確認が必要です。また、専門的な用語に関しては、正確な発音が求められます。このような言葉を練習することで、英語スピーキング練習における自信を高めることができます。特に、shadowspeaksメソッドを用いることで、これらの発音を効果的にマスターできるでしょう。
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。