Set operation column matching rules in SQL - Step-by-Step Execution

Concept Flow - Set operation column matching rules

Start: Two SELECT queries

↓

Check number of columns

↓

Check data types compatibility

↓

Perform set operation (UNION, INTERSECT, EXCEPT)

↓

Return combined result with columns from first query

The database checks that both queries have the same number of columns and compatible data types before combining their results.

Execution Sample

SQL

SELECT id, name FROM employees
UNION
SELECT emp_id, emp_name FROM contractors;

Combines rows from employees and contractors tables with matching columns using UNION.

Execution Table

Step	Action	First Query Columns	Second Query Columns	Check Result	Outcome
1	Identify columns	id (int), name (text)	emp_id (int), emp_name (text)	Number of columns equal	Proceed
2	Check data types	int, text	int, text	Data types compatible	Proceed
3	Combine rows	All rows from first query	All rows from second query	Columns matched by position	Result set returned
4	End	-	-	-	Execution complete

💡 Execution stops after combining rows because column counts and types match.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
First Query Columns	Unknown	id (int), name (text)	id (int), name (text)	id (int), name (text)
Second Query Columns	Unknown	emp_id (int), emp_name (text)	emp_id (int), emp_name (text)	emp_id (int), emp_name (text)
Check Result	None	Number of columns equal	Data types compatible	Columns matched by position

Key Moments - 3 Insights

Why must the number of columns be the same in both queries?

Because set operations combine rows by matching columns positionally, different column counts would cause mismatch and errors (see execution_table step 1).

What happens if data types are not compatible?

The database will raise an error and stop execution because it cannot combine columns with incompatible types (see execution_table step 2).

Which query's column names appear in the final result?

The column names from the first query are used in the combined result set (see execution_table step 3).

Visual Quiz - 3 Questions

Look at the execution table, what is checked at step 2?

A Number of columns equality

B Data types compatibility

C Row count equality

D Column names matching

💡 Hint

Refer to the 'Check data types' action in execution_table row 2.

At which step does the database combine rows from both queries?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look for 'Combine rows' action in execution_table.

If the second query had 3 columns instead of 2, what would happen?

A Execution proceeds normally

B Data types compatibility is checked

C Error due to column count mismatch

D Column names from second query used

💡 Hint

See execution_table step 1 about number of columns equality.

Concept Snapshot

Set operations (UNION, INTERSECT, EXCEPT) require both queries to have the same number of columns.
Columns are matched by position, not by name.
Data types of corresponding columns must be compatible.
Final result uses column names from the first query.
If checks fail, the operation errors out.

Full Transcript

When using set operations in SQL like UNION, the database first checks that both SELECT queries have the same number of columns. Then it verifies that the data types of these columns are compatible. If both checks pass, it combines the rows from both queries by matching columns in order. The final result uses the column names from the first query. If the number of columns or data types do not match, the database raises an error and stops execution.

Practice

1.

Which rule must be followed when using SQL set operations like UNION or INTERSECT?

easy

A. Both queries must have the same number of columns with compatible data types.

B. The second query must have more columns than the first.

C. Column names must be identical in both queries.

D. Set operations only work with numeric columns.

Solution

1. Step 1: Understand set operation requirements

   Set operations combine results from multiple queries, so columns must match in number and type to align data correctly.

2. Step 2: Check column name and type rules

   Column names do not need to match; only the first query's column names are used. Data types must be compatible, and the number of columns must be the same.

3. Final Answer:

   Both queries must have the same number of columns with compatible data types. -> Option A

4. Quick Check:

   Column count and type compatibility = A [OK]

Hint: Match column count and types for set operations [OK]

Common Mistakes:

• Assuming column names must match
• Using different number of columns
• Trying set operations on incompatible data types

2.

Which of the following SQL queries correctly uses UNION with matching columns?

-- Table A: (id INT, name VARCHAR)
-- Table B: (user_id INT, username VARCHAR)

A) SELECT id, name FROM A UNION SELECT user_id, username FROM B;
B) SELECT id FROM A UNION SELECT user_id, username FROM B;
C) SELECT id, name FROM A UNION SELECT user_id FROM B;
D) SELECT id, name FROM A UNION SELECT user_id, username, email FROM B;

easy

A. SELECT id, name FROM A UNION SELECT user_id FROM B;

B. SELECT id FROM A UNION SELECT user_id, username FROM B;

C. SELECT id, name FROM A UNION SELECT user_id, username FROM B;

D. SELECT id, name FROM A UNION SELECT user_id, username, email FROM B;

Solution

1. Step 1: Check column counts in each query

   SELECT id, name FROM A UNION SELECT user_id, username FROM B; selects 2 columns from both queries, matching counts. Other options have mismatched column counts (1 vs 2, 2 vs 1, or 2 vs 3).

2. Step 2: Verify column types compatibility

   Columns in SELECT id, name FROM A UNION SELECT user_id, username FROM B; are INT and VARCHAR in both queries, which are compatible.

3. Final Answer:

   SELECT id, name FROM A UNION SELECT user_id, username FROM B; -> Option C

4. Quick Check:

   Equal columns and compatible types = A [OK]

Hint: Count columns and check types match in both queries [OK]

Common Mistakes:

• Mismatched column counts cause errors
• Ignoring column type compatibility
• Assuming extra columns are allowed

3.

Given the tables and query below, what will be the output?

Table X:
id | value
1  | 'A'
2  | 'B'

Table Y:
code | val
2    | 'B'
3    | 'C'

Query:
SELECT id, value FROM X
UNION
SELECT code, val FROM Y;

medium

A. Syntax error due to column name mismatch

B. [ (1, 'A'), (2, 'B'), (3, 'C') ]

C. [ (1, 'A'), (3, 'C') ]

D. [ (1, 'A'), (2, 'B'), (2, 'B'), (3, 'C') ]

Solution

1. Step 1: Check column counts and types

   Both queries select 2 columns with compatible types (INT and VARCHAR). Column names differ but that is allowed.

2. Step 2: Understand UNION behavior

   UNION removes duplicates. Rows (2, 'B') appear in both tables, so only one copy appears in result.

3. Final Answer:

   [ (1, 'A'), (2, 'B'), (3, 'C') ] -> Option B

4. Quick Check:

   UNION removes duplicates = D [OK]

Hint: UNION removes duplicates, column names don't matter [OK]

Common Mistakes:

• Expecting duplicate rows in UNION result
• Thinking column names must match
• Confusing UNION with UNION ALL

4.

Identify the error in the following SQL set operation:

SELECT id, name FROM Customers
UNION
SELECT customer_id FROM Orders;

medium

A. Column names do not match between queries.

B. UNION cannot be used with SELECT statements.

C. Data types of columns are incompatible.

D. The second query has fewer columns than the first.

Solution

1. Step 1: Compare column counts in both queries

   The first query selects 2 columns (id, name), the second selects only 1 column (customer_id). This mismatch causes an error.

2. Step 2: Check other possible errors

   Column names do not need to match, and UNION works with SELECT statements. Data types are unknown but column count mismatch is enough to cause error.

3. Final Answer:

   The second query has fewer columns than the first. -> Option D

4. Quick Check:

   Column count mismatch = B [OK]

Hint: Ensure both queries select same number of columns [OK]

Common Mistakes:

• Thinking column names must match
• Ignoring column count mismatch
• Assuming UNION works with different column counts

5.

You have two tables:

Employees(emp_id INT, emp_name VARCHAR, dept VARCHAR)
Managers(manager_id INT, manager_name VARCHAR)

You want to combine employee and manager names into one list using a set operation. Which query correctly applies set operation column matching rules?

A) SELECT emp_id, emp_name FROM Employees UNION SELECT manager_id, manager_name FROM Managers;
B) SELECT emp_name FROM Employees UNION SELECT manager_name FROM Managers;
C) SELECT emp_name, dept FROM Employees UNION SELECT manager_name, manager_id FROM Managers;
D) SELECT emp_id, emp_name, dept FROM Employees UNION SELECT manager_id, manager_name FROM Managers;

hard

A. SELECT emp_name FROM Employees UNION SELECT manager_name FROM Managers;

B. SELECT emp_id, emp_name FROM Employees UNION SELECT manager_id, manager_name FROM Managers;

C. SELECT emp_name, dept FROM Employees UNION SELECT manager_name, manager_id FROM Managers;

D. SELECT emp_id, emp_name, dept FROM Employees UNION SELECT manager_id, manager_name FROM Managers;

Solution

1. Step 1: Identify columns to combine

   You want a list of names only, so selecting one column (name) from each table is appropriate.

2. Step 2: Check column counts and types

   SELECT emp_name FROM Employees UNION SELECT manager_name FROM Managers; selects one VARCHAR column from each table, matching count and compatible types. Other options have mismatched column counts or incompatible columns.

3. Final Answer:

   SELECT emp_name FROM Employees UNION SELECT manager_name FROM Managers; -> Option A

4. Quick Check:

   Same column count and type for names = B [OK]

Hint: Select same number and type of columns to combine [OK]

Common Mistakes:

• Selecting different numbers of columns
• Mixing incompatible column types
• Including unrelated columns in set operation