Functional dependency definition in DBMS Theory - Step-by-Step Execution

Concept Flow - Functional dependency definition

Start with a Relation

↓

Identify Attributes

↓

Check if Value of Attribute Set A

↓

Determines Value of Attribute Set B?

Yes No↓

Functional Dependency

↓

Use in Database Design

This flow shows how we start with a table, identify attributes, and check if one set of attributes determines another, which defines a functional dependency.

Execution Sample

DBMS Theory

Relation: Student(ID, Name, Age)
Check if ID -> Name
For each ID, is Name unique?
If yes, ID functionally determines Name

This example checks if the student ID uniquely determines the student's name, illustrating a functional dependency.

Analysis Table

Step	Action	Check	Result
1	Look at Student relation	Attributes: ID, Name, Age	Proceed
2	Select attribute set A = ID	Is ID unique for each row?	Yes
3	Select attribute set B = Name	Does each ID have exactly one Name?	Yes
4	Conclusion	ID -> Name holds	Functional dependency confirmed
5	Check if Name -> Age	Does each Name have exactly one Age?	No
6	Conclusion	Name -> Age does not hold	No functional dependency

💡 Checked all attribute pairs; functional dependency confirmed only for ID -> Name

State Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
ID uniqueness	Unknown	Yes	Yes	Yes	Yes
Name uniqueness per ID	Unknown	Unknown	Yes	Yes	Yes
Functional dependency ID->Name	Unknown	Unknown	Confirmed	Confirmed	Confirmed
Functional dependency Name->Age	Unknown	Unknown	Unknown	Not confirmed	Not confirmed

Key Insights - 2 Insights

Why does ID -> Name hold but Name -> Age does not?

Because each ID corresponds to exactly one Name (step 3), but a Name can appear with different Ages (step 5), so only ID functionally determines Name.

What does it mean if a functional dependency does not hold?

It means the attribute set on the left does not uniquely determine the attribute set on the right, as shown in step 5 where Name does not determine Age.

Visual Quiz - 3 Questions

Look at the execution table at step 3, what is the result of checking if each ID has exactly one Name?

A Yes, each ID has exactly one Name

B No, IDs have multiple Names

C Not checked yet

D IDs have no Names

💡 Hint

Refer to the 'Result' column in step 3 of the execution_table

At which step does the functional dependency Name -> Age get rejected?

A Step 4

B Step 5

C Step 2

D Step 6

💡 Hint

Look at the 'Check' and 'Result' columns in step 5 of the execution_table

If every Name had exactly one Age, how would the execution table change?

A Step 4 would reject ID -> Name

B Step 3 would change to No

C Step 5 result would be Yes and step 6 would confirm Name -> Age

D No change in the table

💡 Hint

Consider the logic in steps 5 and 6 about functional dependency confirmation

Concept Snapshot

Functional Dependency means one attribute set uniquely determines another.
Written as A -> B meaning if two rows agree on A, they must agree on B.
Used to design databases and ensure data consistency.
Check by verifying uniqueness of B values for each A value.
If not unique, dependency does not hold.

Full Transcript

Functional dependency is a rule in databases where one set of attributes uniquely determines another set. We start by looking at a table and its attributes. Then we check if for every value of attribute set A, there is exactly one corresponding value of attribute set B. If yes, we say A functionally determines B, written as A -> B. For example, in a Student table with ID, Name, and Age, if each ID has exactly one Name, then ID -> Name holds. But if a Name can have different Ages, then Name -> Age does not hold. This concept helps in organizing data and avoiding redundancy.