Division operation in DBMS Theory - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Division operation in a database?

The Division operation finds all values in one relation that are related to all values in another relation. It is used to answer queries like "Find all X that are related to every Y."

beginner

Which type of queries is the Division operation useful for?

It is useful for queries that ask for entities related to all items in a set, such as "Find students who have taken all courses offered."

intermediate

How does the Division operation relate two tables?

It returns the set of values from the first table that match every value in the second table based on a common attribute.

beginner

What is a real-life example of the Division operation?

If you want to find employees who have worked on all projects, the Division operation helps by returning employees linked to every project in the projects list.

intermediate

What is the difference between Division and other relational operations like Join?

Join combines rows based on matching columns, while Division finds rows in one table related to all rows in another table, focusing on completeness rather than pairing.

What does the Division operation in databases return?

A All records from both tables combined

B All records from the first table related to every record in the second table

C Only matching records from both tables

D Records from the second table not in the first

Division returns records from the first table that relate to all records in the second table.

Which query is best solved using Division?

A Find students enrolled in all courses

B Find students enrolled in any course

C Find courses with no students

D Find students enrolled in exactly one course

Division is used to find entities related to all items in another set, like students enrolled in all courses.

In Division operation, what must the second relation represent?

A The set of items to exclude

B The set of items to be deleted

C The set of items to join partially

D The set of all items to be matched completely

The second relation represents the set of items that must be matched completely by the first relation.

Which relational algebra operation is most different from Division?

A Selection

B Projection

C Join

D Union

Join pairs rows based on matching columns, while Division finds rows related to all rows in another table.

If you want to find employees who worked on every project, which operation helps?

A Division

B Union

C Selection

D Cartesian Product

Division helps find entities related to all items in another set, like employees who worked on every project.

Explain the Division operation in databases and give a simple example.

Think about finding all entities related to every item in another set.

How does Division differ from Join in relational algebra?

Consider what each operation returns and how they combine tables.

Practice

1.

What does the division operation in a database primarily help to find?

easy

A. Entries that appear only once in a table

B. The sum of values in a column

C. The total count of rows in a table

D. Entries in one table related to all entries in another table

Solution

1. Step 1: Understand the division operation purpose

   The division operation is used to find records in one table that are related to every record in another table.

2. Step 2: Compare with other options

   The other options describe operations like finding unique entries, counting rows, or summing values, not the division operation.

3. Final Answer:

   Entries in one table related to all entries in another table -> Option D

4. Quick Check:

   Division operation = find all related entries [OK]

Hint: Division finds entries matching all in another set [OK]

Common Mistakes:

• Confusing division with counting or summing
• Thinking it finds entries related to some, not all
• Mixing division with join operations

2.

Which SQL keyword is commonly used to implement the division operation?

easy

A. GROUP BY

B. NOT EXISTS

C. HAVING

D. EXISTS

Solution

1. Step 1: Recall division implementation in SQL

   Division is often implemented using NOT EXISTS to check that no unmatched entries exist.

2. Step 2: Analyze other keywords

   GROUP BY groups rows, HAVING filters groups, and EXISTS checks existence but not for division logic.

3. Final Answer:

   NOT EXISTS -> Option B

4. Quick Check:

   Division uses NOT EXISTS for completeness check [OK]

Hint: Use NOT EXISTS to ensure all related entries exist [OK]

Common Mistakes:

• Using EXISTS instead of NOT EXISTS
• Confusing GROUP BY with division logic
• Assuming HAVING filters individual rows

3.

Consider two tables: Suppliers(supplier_id) and Parts(part_id), and a relation Supplies(supplier_id, part_id). Which SQL query finds suppliers who supply all parts?

SELECT supplier_id FROM Suppliers S WHERE NOT EXISTS (
  SELECT part_id FROM Parts P WHERE NOT EXISTS (
    SELECT * FROM Supplies SP WHERE SP.supplier_id = S.supplier_id AND SP.part_id = P.part_id
  )
);

medium

A. Finds parts not supplied by any supplier

B. Finds suppliers supplying no parts

C. Finds suppliers supplying all parts

D. Finds parts supplied by all suppliers

Solution

1. Step 1: Understand the nested NOT EXISTS logic

   The inner NOT EXISTS checks if a supplier does not supply a part. The outer NOT EXISTS ensures no such part exists, meaning the supplier supplies all parts.

2. Step 2: Match query purpose with options

   This query finds suppliers who supply every part, matching Finds suppliers supplying all parts.

3. Final Answer:

   Finds suppliers supplying all parts -> Option C

4. Quick Check:

   Double NOT EXISTS = all parts supplied [OK]

Hint: Double NOT EXISTS means 'for all' condition [OK]

Common Mistakes:

• Misreading NOT EXISTS as EXISTS
• Confusing suppliers with parts
• Ignoring nested query logic

4.

Identify the error in this SQL query intended to find students who have completed all courses:

SELECT student_id FROM Students S WHERE EXISTS (
  SELECT course_id FROM Courses C WHERE NOT EXISTS (
    SELECT * FROM Completed WHERE student_id = S.student_id AND course_id = C.course_id
  )
);

medium

A. Should use NOT EXISTS instead of EXISTS in outer query

B. Missing GROUP BY clause

C. Incorrect table alias usage

D. Should use INNER JOIN instead of subqueries

Solution

1. Step 1: Analyze the logic of EXISTS and NOT EXISTS

   The inner NOT EXISTS checks if a student hasn't completed a course. The outer EXISTS checks if such a course exists, meaning the student missed some courses.

2. Step 2: Correct the logic for 'all courses completed'

   To find students who completed all courses, the outer condition should be NOT EXISTS to ensure no missing courses.

3. Final Answer:

   Should use NOT EXISTS instead of EXISTS in outer query -> Option A

4. Quick Check:

   Use NOT EXISTS outside to confirm completeness [OK]

Hint: Outer NOT EXISTS ensures no missing entries [OK]

Common Mistakes:

• Using EXISTS instead of NOT EXISTS outside
• Assuming GROUP BY is needed here
• Confusing alias names

5.

You have two tables: Employees(emp_id) and Projects(proj_id), and a relation WorksOn(emp_id, proj_id). How would you find employees who work on every project that a specific manager manages, given a table Manages(manager_id, proj_id)?

hard

A. Use division operation with WorksOn and projects managed by the manager

B. Use a simple JOIN between Employees and Projects

C. Use GROUP BY on WorksOn without filtering projects

D. Use EXISTS to find employees working on any project

Solution

1. Step 1: Identify the problem as a division operation

   We want employees who work on all projects managed by a specific manager, which is a classic division problem.

2. Step 2: Apply division using WorksOn and filtered projects

   Filter projects by the manager in Manages, then find employees whose WorksOn covers all those projects.

3. Final Answer:

   Use division operation with WorksOn and projects managed by the manager -> Option A

4. Quick Check:

   Division finds employees working on all manager's projects [OK]

Hint: Filter projects by manager, then apply division on WorksOn [OK]

Common Mistakes:

• Ignoring filtering projects by manager
• Using JOIN without division logic
• Assuming GROUP BY alone solves the problem