Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
UNION Clause | Nested Subqueries
Intermediate SQL
course content

Course Content

Intermediate SQL

Intermediate SQL

1. Grouping
2. Nested Subqueries
3. Joining Tables
4. DDL and DML in SQL

book
UNION Clause

We've caught the attention of a client who needs SQL queries. Before we dive into JOINs, let's learn about the UNION clause, which is essential for combining multiple tables.

Here are some important things to know about using UNION:

  1. Columns Count and Order: All queries combined with UNION must have the same number of columns in the same order;

  2. Data Types: The columns in each query must have compatible data types;

  3. Unique Rows: By default, UNION removes duplicate rows. Use UNION ALL if you want to keep duplicates.

For a better understanding of how to correctly combine tables using the UNION clause, I introduced an additional table that contains information about contractors.

There's not much information here, just the first_name, last_name, and email.

You can see that this table has similarities with the employees table. Using the UNION clause, we can combine these two tables to, for example, see a list of all names and surnames of employees and contractors involved in the company.

To do this, we'll use the UNION clause:

12345678
(SELECT employee_id as id, first_name, last_name FROM employees) UNION (SELECT contractor_id as id, first_name, last_name FROM contractors) ORDER BY id
copy

Let's break down what's happening:

We have two queries that each return three columns with the same data types. We want to see the Id, first_name, and last_name of everyone in the company. We also renamed the Id column so both queries have the same column names.

Then, we use UNION to combine the results of these queries, removing duplicates (though there are none here).

Finally, we sort the results by Id using ORDER BY.

Note

We're sorting by Id, which is a common column in both tables.

After using UNION, we get a "single large query" that we can further manipulate with clauses like ORDER BY.

We can't directly use WHERE or GROUP BY with tables combined using UNION. To apply these clauses, we need to use a subquery in the FROM section. Here's an example of how to do it:

123456789
SELECT id, first_name, last_name FROM ( SELECT employee_id AS id, first_name, last_name FROM employees UNION SELECT contractor_id AS id, first_name, last_name FROM contractors ) AS combined WHERE first_name = 'Jane'
copy

Using a subquery in the FROM section gives us more flexibility! It might seem tricky at first, but mastering this will make writing complex queries much easier.

1. What columns are required when using the UNION clause in SQL?

2. How does the UNION clause treat duplicate rows by default?

What columns are required when using the `UNION` clause in SQL?

What columns are required when using the UNION clause in SQL?

Select the correct answer

How does the `UNION` clause treat duplicate rows by default?

How does the UNION clause treat duplicate rows by default?

Select the correct answer

Everything was clear?

How can we improve it?

Thanks for your feedback!

Section 2. Chapter 5
We're sorry to hear that something went wrong. What happened?
some-alt