Closure of attributes in DBMS Theory - Time & Space Complexity

Time Complexity: Closure of attributes

O(n^3)

Understanding Time Complexity

When working with database attributes, finding the closure helps us know all attributes we can get from a starting set.

We want to understand how the time needed grows as the number of attributes and rules increases.

Scenario Under Consideration

Analyze the time complexity of the following closure calculation.

-- Given a set of attributes and functional dependencies
-- Find closure of attribute set X
closure = X
repeat
  for each functional dependency (A -> B):
    if A is subset of closure and B not in closure:
      add B to closure
until no new attributes added
    

This code finds all attributes reachable from X using the given rules.

Identify Repeating Operations

Look for loops and repeated checks.

• Primary operation: Checking each functional dependency repeatedly.
• How many times: Until no new attributes are added, potentially multiple passes over all dependencies.

How Execution Grows With Input

As the number of attributes and dependencies grows, the checks increase.

Input Size (n)	Approx. Operations
10	About 100 checks
100	About 10,000 checks
1000	About 1,000,000 checks

Pattern observation: The work grows roughly with the square of the input size.

Final Time Complexity

Time Complexity: O(n^3)

This means the time needed grows roughly with the cube of the number of attributes and dependencies.

Common Mistake

[X] Wrong: "The closure calculation finishes in linear time because we just check each dependency once."

[OK] Correct: We often need to check dependencies multiple times as new attributes get added, so the process repeats until no changes occur.

Interview Connect

Understanding how closure calculation scales helps you explain database normalization and dependency analysis clearly in interviews.

Self-Check

"What if we stored dependencies in a way that lets us quickly find which ones apply? How would that affect the time complexity?"

Practice

1. What does the closure of attributes represent in database design?

easy

A. The total number of tables in a database

B. All attributes functionally determined by a given set of attributes

C. The list of all primary keys in a database

D. The count of foreign keys referencing a table

Solution

1. Step 1: Understand the concept of closure

   The closure of a set of attributes includes all attributes that can be functionally determined from it using given dependencies.

2. Step 2: Relate closure to database design

   This helps identify all attributes dependent on a set, useful for normalization and design.

3. Final Answer:

   All attributes functionally determined by a given set of attributes -> Option B

4. Quick Check:

   Closure = all functionally determined attributes [OK]

Hint: Closure means all attributes you can find from given ones [OK]

Common Mistakes:

• Confusing closure with number of tables
• Thinking closure lists keys only
• Mixing closure with foreign key counts

2. Which of the following is the correct notation for the closure of attribute set A given functional dependencies F?

easy

A. A+

B. F+

C. A*

D. F*

Solution

1. Step 1: Recall standard notation

   The closure of an attribute set A under functional dependencies F is denoted as A+.

2. Step 2: Differentiate from other notations

   F+ denotes closure of the set of functional dependencies, not attributes. A* and F* are not standard notations here.

3. Final Answer:

   A+ -> Option A

4. Quick Check:

   Attribute closure = A+ notation [OK]

Hint: Closure of attributes is always written as A+ [OK]

Common Mistakes:

• Using F+ for attribute closure
• Confusing closure notation with star (*)
• Mixing attribute and dependency closures

3. Given attributes A, B, C, D and functional dependencies:
A -> B, B -> C, C -> D. What is the closure of {A}?

medium

A. {A, B, C, D}

B. {A, B, C}

C. {A, B}

D. {A, D}

Solution

1. Step 1: Start with initial set {A}

   Closure begins with {A}.

2. Step 2: Apply functional dependencies repeatedly

   From A -> B, add B; from B -> C, add C; from C -> D, add D.

3. Final Answer:

   {A, B, C, D} -> Option A

4. Quick Check:

   Applying all dependencies gives full set [OK]

Hint: Keep adding attributes until no new ones appear [OK]

Common Mistakes:

• Stopping after first dependency
• Forgetting to add transitive dependencies
• Confusing closure with just initial attributes

4. Identify the error in this closure calculation: Given A -> B, B -> C, and starting with {A}, the closure is calculated as {A, C}.

medium

A. Closure should be empty

B. Incorrect initial attribute set

C. Wrong functional dependencies used

D. Missed adding attribute B before C

Solution

1. Step 1: Check closure calculation steps

   Starting with {A}, applying A -> B adds B first.

2. Step 2: Verify transitive dependencies

   Only after B is added can B -> C add C. Skipping B is incorrect.

3. Final Answer:

   Missed adding attribute B before C -> Option D

4. Quick Check:

   Closure must add intermediate attributes [OK]

Hint: Add attributes step-by-step, don't skip intermediates [OK]

Common Mistakes:

• Skipping intermediate attributes
• Assuming direct jump to last attribute
• Ignoring order of dependencies

5. Given attributes A, B, C, D, E and functional dependencies:
A -> BC, CD -> E, B -> D. What is the closure of {A, D}?

hard

A. {A, C, D, E}

B. {A, B, C, D}

C. {A, B, C, D, E}

D. {A, B, C, E}

Solution

1. Step 1: Start with {A, D}

   Initial closure is {A, D}.

2. Step 2: Apply A -> BC

   Add B and C, closure becomes {A, B, C, D}.

3. Step 3: Apply B -> D

   D already included, no change.

4. Step 4: Apply CD -> E

   Since C and D are in closure, add E.

5. Final Answer:

   {A, B, C, D, E} -> Option C

6. Quick Check:

   All attributes reachable from {A, D} included [OK]

Hint: Use all dependencies repeatedly until no new attributes [OK]

Common Mistakes:

• Not applying CD -> E after adding C
• Forgetting to add B and C from A
• Stopping closure too early