Pratique du Shadowing: Database Normalisation: Third Normal Form - Apprendre l'anglais à l'oral avec la vidéo

Choisissez un mode d'entraînement

Chaque mode ouvre une salle d'entraînement en plein écran.

99 phrases

Si les phrases sont trop courtes ou trop longues, cliquez sur Edit pour les ajuster.

Thank you.

Merci.

This video is about database normalisation.

specifically normalising a database to a third normal form.

It follows on from the video about second normal form by working through the same example.

to qualify for third normal form in technical terms.

The data must already be in second normal form and a relation has no transitive functional dependencies on the primary key.

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

if you change the non -key attribute.

Let's continue with our example.

To get these tables into third normal form, they must already be in second normal form.

Which they are.

Now you need to ensure that there are no transitive functional dependencies.

Well, actually in this case there aren't any, so these tables are already in third normal form as well.

But what's meant by a transitive functional dependency?

And how can you spot one?

Let's start by reviewing the term functional dependency.

In the students table, The first name is functionally dependent on the ID.

The ID is called the determinant, and the first name is called the dependent.

This is normally written like this.

Another way of saying it is that there is exactly one first name for any given instance of a student.

In the same way, last name is functionally dependent on ID, and so is marital status.

In the student course table there's a composite primary key which the grade is functionally dependent on.

It can be written like this.

You could also say that the course title in the student course table is functionally dependent on the composite primary key.

but because the course title is a subset of the composite key It's known as a trivial functional dependency.

It's OK to have functional dependencies in a table in order for it to be in third normal form.

In fact, it's absolutely necessary.

Every non -key attribute of a table must be fully functionally dependent on the primary key.

If it was partially dependent, the table wouldn't even be in second normal form.

So what's a transient functional dependency?

These are not allowed in third normal form.

Let's add some more data to the courses table to help make this clear.

The course title is still the primary key of the courses table.

It's unique for each course, it certainly belongs here.

As an aside, if there were two courses with the same course title, perhaps a computer science A level and a computer science diploma.

then you'd have to rethink the primary key, perhaps by giving each course a unique code.

But let's proceed on the basis that each course title will always be unique.

The fee and the qualification are both attributes of the course title.

They're functionally dependent on the primary key, so they belong here.

but the teacher ID and the teacher name columns seem a little out of place.

Each course is always taught by the same teacher, according to this data at least.

So you'd be forgiven for allowing them into this table in the first place.

Teacher ID is an attribute of a course, and it's functionally dependent on the primary key.

Teacher name is also an attribute of a course, and it too depends on the primary key.

There are no partial dependencies on the primary key here, so the table is indeed in second -normal form.

But there's a potential problem.

If you decide to change the teacher for a course, then you have to change both the teacher ID and the teacher name.

They are functionally dependent on each other.

This is not ideal because as you know, editing mistakes can lead to inconsistencies in the data.

If you change one of the course titles, it becomes a different course.

So again, you need to change the teacher ID and the teacher name.

To put this in technical jargon, the teacher ID is functionally dependent on the course title,

and the teacher name is functionally dependent on the teacher ID.

So there's a transitive dependency between the teacher name and the course title.

Something depends on something which depends on something else.

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.

So there's a transitive dependency between the teacher ID and the course title.

It's just another way of looking at these particular data.

whichever way you look at them, there are transitive functional dependencies here.

So the courses table violates third normal form.

This is how to solve the problem.

You need a separate teacher's table.

The teacher column in the courses table establishes the relationship with this new table.

None of these tables contain transitive functional dependencies.

the database is definitely in third normal form.

Another example of a transitive functional dependency would be

if the student course table contained an exam mark as well as the grade.

The grade is derived from the mark.

Now arguably you shouldn't store any attribute in the database if you can calculate it from something else.

Nevertheless, let's suppose you had good reason to store both the exam mark and the grade in this table.

If you change the value of the primary key for one of these records, it's a different student course combination.

So you need to change the exam mark and the grade to match.

The mark is functionally dependent on the primary key and the grade is functionally dependent on the mark.

There's a transitive functional dependency between the grade and the primary key Strictly speaking,

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.

Let's stick with just the grade in this database.

Now take a look at this version of the Students table.

A purist might tell you that if you were storing postal addresses in the students' table, then these should be moved into another table.

Every part of the address is functionally dependent on the primary key.

but there are some transitive functional dependencies here.

If a student emigrates to a new country, then they'd necessarily moved to a new town and a new street address.

But you have to ask yourself if breaking up this table is actually practical.

For a start, addresses often have missing information.

But even if your data are complete, decompose them too much and they start to become unmanageable.

To get into third normal form, there are some simple clues you can look out for.

Are there any items that are obviously categories?

Is there anything that looks like an identifier?

Is there any more duplication of data?

But be careful with this.

Every student has a gender, but it doesn't really make sense to put genders in a separate table.

If you'd started with a flat file containing all of these data in the first place,

You may well have come up with this four -table structure straight away.

With experience, you'll eventually find you can normalise a database directly to third normal form or near enough,

just by looking at the data and applying a little common sense.

In summary, To be in third normal form,

The data must already be in second normal form and a relation has no transitive functional dependencies on the primary key.

or put more simply the data must already be in second normal form

and there is no other non -key attribute

that you would need to change in the table if you change to non -key attribute.

Télécharger l'application

Tout pour parler couramment

Prononciation IAChaque phrase notée

Phonétique (IPA)Maîtrisez chaque son

VocabulaireEnrichissez votre lexique

Jeu de vocabulaireApprenez en jouant

Scanner le QR

Download on theApp Store Get it onGoogle Play

FOR YOU

Vidéo recommandée

53 phrases

Vocabulaire et conseils d’expression pour cette leçon

Cette leçon d’expression orale de niveau C1 s’appuie sur la vidéo « Database Normalisation: Third Normal Form ». Les mots qui reviennent le plus souvent : table, key, normal, teacher, dependent. Cette vidéo contient 99 phrases et 1299 mots à répéter en shadowing. La partie parlée dure 8:27. Le locuteur parle à un rythme naturel d’environ 154 mots par minute, proche d’une conversation courante. 84 % des mots font partie des 3 000 mots les plus courants en anglais ; le reste mérite d’être vu avant de commencer.

Vocabulaire clé de cette vidéo

Les 15 mots les plus avancés de la vidéo, avec leur prononciation et leur sens :

Mot	Prononciation	Sens
transitive adjectif	/ˈtɹænzɪtɪv/	transitif
attribute nom	/ˈæt.ɹɪˌbjut/	attribut
decompose verbe	/ˌdiːkəmˈpəʊz/	décomposer
determinant nom	/dɪˈtɜːmɪnənt/	déterminant
duplication nom	/d(j)u.plɪˈkeɪ.ʃən/	duplication
emigrate verbe	/ˈɛmɪɡɹeɪt/	émigrer
inconsistency nom	/ˌɪnkənˈsɪstənsi/	inconsistance
jargon nom	/ˈdʒɑː.ɡən/	jargon
normalization nom	/ˌnɔɹ.mə.ləˈzeɪ.ʃən/	normalisation
normalize verbe	/ˈnɔː.mə.laɪz/	normaliser
purist nom	/ˈpjʊɹ.ɪst/	puriste
rethink verbe	/ɹiːˈθɪŋk/	repenser, réfléchir
transient adjectif	/ˈtɹæn.ʃənt/	passager, provisoire
unmanageable adjectif		ingérable
derive verbe	/dɪˈɹaɪv/	tirer, trouver

Les verbes à particule que vous entendrez

Mot	Sens
break up verbe	rompre, couper
come up with verbe	inventer, imaginer

Des phrases à répéter

Des phrases courtes et complètes de la vidéo, à réutiliser dans la conversation de tous les jours :

Let's continue with our example.
Let's start by reviewing the term functional dependency.
You need a separate teacher's table.
Let's stick with just the grade in this database.

Prononciation à surveiller

Le locuteur utilise 11 contractions et formes réduites, comme you'd, aren't, doesn't. Prononcez-les sous leur forme courte, telles que vous les entendez.

Les sons « sh » et « zh »: duplication /d(j)u.plɪˈkeɪ.ʃən/, normalization /ˌnɔɹ.mə.ləˈzeɪ.ʃən/, transient /ˈtɹæn.ʃənt/, qualification /ˌkwɑlɪfɪˈkeɪʃən/
Mots longs — placez bien l’accent: dependency /dɪˈpɛndənsi/, determinant /dɪˈtɜːmɪnənt/, duplication /d(j)u.plɪˈkeɪ.ʃən/, inconsistency /ˌɪnkənˈsɪstənsi/, normalization /ˌnɔɹ.mə.ləˈzeɪ.ʃən/

Les sons difficiles pour les francophones :

/tʃ/ et /dʒ/ — à ne pas adoucir en « ch » et « j »: jargon /ˈdʒɑː.ɡən/, whichever /wɪt͡ʃˈɛvɚ/
/r/ anglais — langue recourbée, sans frotter la gorge: transitive /ˈtɹænzɪtɪv/, attribute /ˈæt.ɹɪˌbjut/, emigrate /ˈɛmɪɡɹeɪt/, normalization /ˌnɔɹ.mə.ləˈzeɪ.ʃən/, purist /ˈpjʊɹ.ɪst/

Comment s’entraîner avec cette vidéo

Écoutez la vidéo en entier une fois sans parler et notez les mots que vous ne connaissez pas.
Commencez à la vitesse 0,75×, répétez phrase par phrase, puis revenez à la vitesse normale quand cela devient facile.
Enregistrez-vous et comparez avec l’original, en faisant attention à des mots comme transitive, attribute, decompose.

Qu'est-ce que la technique du Shadowing ?

Le Shadowing est une technique d'apprentissage des langues fondée sur la science, développée à l'origine pour la formation des interprètes professionnels. Le principe est simple mais puissant : vous écoutez de l'anglais natif et le répétez immédiatement à voix haute — comme une ombre suivant le locuteur avec un décalage de 1 à 2 secondes. Les recherches montrent une amélioration significative de la précision de la prononciation, de l'intonation, du rythme, des liaisons, de la compréhension orale et de la fluidité.

Technique du shadowing : lire le guide complet étape par étape →

Pratique du Shadowing: Database Normalisation: Third Normal Form - Apprendre l'anglais à l'oral avec la vidéo

Choisissez un mode d'entraînement

Télécharger l'application

System Design Was HARD - Until You Knew the Trade-Offs

Overview of Fluid and Electrolyte Physiology (Fluid Compartment)

Organizational forms and corporate issuer features (for the CFA Level 1 exam)

Free CCNA | VLANs (Part 2) | Day 17 | CCNA 200-301 Complete Course

Cohesion 3 - Substitution

OWASP Top 10 Explained

Differential equations, a tourist's guide | DE1

1 7 What is Information

DRY Often Makes Your Code Worse

Understand Microsoft Entra ID | AZ-104 | Episode 2

Everything You Need to Know About DNS: Crash Course System Design #4

Introduction