Why views matter in PostgreSQL - Visual Breakdown

Concept Flow - Why views matter in PostgreSQL

Create View

↓

View stores SQL query

↓

Query View like a table

↓

PostgreSQL runs stored query

↓

Return results to user

↓

Simplifies complex queries & reuse

Views store SQL queries that run when you query the view, making complex data easier to access and reuse.

Execution Sample

PostgreSQL

CREATE VIEW recent_orders AS
SELECT order_id, customer_id, order_date
FROM orders
WHERE order_date > CURRENT_DATE - INTERVAL '30 days';

SELECT * FROM recent_orders;

This creates a view for orders in the last 30 days and then selects all data from that view.

Execution Table

Step	Action	Evaluation	Result
1	Create view 'recent_orders'	Stores SQL query in database	View created successfully
2	Run SELECT * FROM recent_orders	PostgreSQL replaces view with stored query	Executes: SELECT order_id, customer_id, order_date FROM orders WHERE order_date > CURRENT_DATE - INTERVAL '30 days'
3	Query runs on 'orders' table	Filters orders newer than 30 days	Returns matching rows
4	Results returned to user	User sees recent orders data	Output rows with recent orders
5	End	No more steps	Query complete

💡 Query ends after returning filtered recent orders from the base table

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
recent_orders (view)	Not defined	Stores SQL query	Replaced by stored query	Query runs on base table	Returns filtered rows

Key Moments - 2 Insights

Why does querying a view run the stored SQL query instead of returning stored data?

Because views in PostgreSQL are virtual tables that store only the SQL query, not data. When you query the view (see execution_table step 2), PostgreSQL runs the stored query on the base tables to get current data.

Can views simplify complex queries?

Yes. Views let you save complex SQL once (step 1) and then reuse it easily by querying the view (step 2), making your work simpler and less error-prone.

Visual Quiz - 3 Questions

Look at the execution table, what happens at step 2 when you query the view?

A PostgreSQL returns stored data from the view

B PostgreSQL runs the stored SQL query on base tables

C The view is deleted

D A new view is created

💡 Hint

See execution_table row 2: 'PostgreSQL replaces view with stored query' and runs it

According to variable_tracker, what does 'recent_orders' hold after step 1?

A A stored SQL query

B Actual data rows

C An empty table

D A temporary table

💡 Hint

variable_tracker shows 'recent_orders' stores SQL query after step 1

If the base table 'orders' changes, what happens when you query the view?

A View shows old data stored at creation

B View stops working

C View shows updated data by running stored query

D View needs to be recreated

💡 Hint

Views run the stored query on base tables each time (execution_table step 3)

Concept Snapshot

CREATE VIEW view_name AS SELECT ...;
Views store SQL queries, not data.
Querying a view runs its stored query on base tables.
Views simplify complex queries and reuse.
Data shown is always current from base tables.

Full Transcript

Views in PostgreSQL are like saved SQL queries. When you create a view, you store a query, not data. Later, when you select from the view, PostgreSQL runs the stored query on the base tables to get fresh data. This helps simplify complex queries and reuse them easily. The execution flow starts with creating the view, then querying it, which triggers running the stored query, filtering data from the base table, and returning results. Variables like the view name hold the query until run. Beginners often wonder why views don't store data; the answer is they are virtual and run queries on demand. Also, views always show current data because they run the query each time. This makes views powerful for organizing and simplifying database work.

Practice

1. What is the main purpose of using a VIEW in PostgreSQL?

easy

A. To save a complex query as a reusable object

B. To permanently store data separately from tables

C. To speed up data insertion into tables

D. To delete rows from multiple tables at once

Solution

1. Step 1: Understand what a VIEW is

   A VIEW in PostgreSQL is a saved SQL query that acts like a virtual table.

2. Step 2: Identify the main use of a VIEW

   It simplifies complex queries by letting you reuse them without rewriting.

3. Final Answer:

   To save a complex query as a reusable object -> Option A

4. Quick Check:

   Views simplify queries = A [OK]

Hint: Views store queries, not data, for easy reuse [OK]

Common Mistakes:

• Thinking views store data separately
• Confusing views with tables
• Assuming views speed up inserts

2. Which of the following is the correct syntax to create a view named active_users showing users with status = 'active'?

easy

A. CREATE VIEW active_users AS SELECT * FROM users WHERE status = 'active';

B. CREATE active_users VIEW AS SELECT * FROM users WHERE status = 'active';

C. VIEW CREATE active_users AS SELECT * FROM users WHERE status = 'active';

D. CREATE VIEW active_users SELECT * FROM users WHERE status = 'active';

Solution

1. Step 1: Recall the correct CREATE VIEW syntax

   The syntax is: CREATE VIEW view_name AS SELECT ...

2. Step 2: Match the syntax with options

   CREATE VIEW active_users AS SELECT * FROM users WHERE status = 'active'; matches the correct syntax exactly.

3. Final Answer:

   CREATE VIEW active_users AS SELECT * FROM users WHERE status = 'active'; -> Option A

4. Quick Check:

   CREATE VIEW ... AS SELECT ... = B [OK]

Hint: Remember: CREATE VIEW name AS SELECT ... [OK]

Common Mistakes:

• Swapping keywords CREATE and VIEW
• Omitting AS keyword
• Incorrect keyword order

3. Given the table orders with columns id, customer, and amount, what will this view return?

CREATE VIEW big_orders AS SELECT customer, amount FROM orders WHERE amount > 100;

Then running:

SELECT * FROM big_orders;

medium

A. Syntax error because id is missing in view

B. All orders showing id, customer, and amount

C. All orders with amount greater than 100 showing customer and amount

D. Only orders with amount less than or equal to 100

Solution

1. Step 1: Understand the view definition

   The view selects customer and amount from orders where amount is greater than 100.

2. Step 2: Predict the SELECT * from the view

   It returns only customer and amount columns for orders with amount > 100.

3. Final Answer:

   All orders with amount greater than 100 showing customer and amount -> Option C

4. Quick Check:

   View filters amount > 100 and selects customer, amount = D [OK]

Hint: View columns = selected columns, filtered by WHERE [OK]

Common Mistakes:

• Expecting all columns to appear
• Confusing filter condition direction
• Thinking missing columns cause errors

4. You created a view with:

CREATE VIEW recent_sales AS SELECT * FROM sales WHERE sale_date > CURRENT_DATE - INTERVAL '7 days';

But running SELECT * FROM recent_sales; returns an error. What is the likely cause?

medium

A. CURRENT_DATE cannot be used in a view definition

B. The view definition is correct; error is elsewhere

C. The view needs to be refreshed manually to update data

D. The INTERVAL syntax is invalid in the view definition

Solution

1. Step 1: Check if INTERVAL and CURRENT_DATE are valid

   Both INTERVAL and CURRENT_DATE are valid in PostgreSQL and can be used in views.

2. Step 2: Understand view behavior

   Views are virtual and always reflect current data; no manual refresh needed.

3. Final Answer:

   The view definition is correct; error is elsewhere -> Option B

4. Quick Check:

   Valid syntax means error is not in view code = A [OK]

Hint: Check error source; valid syntax means problem is outside view [OK]

Common Mistakes:

• Assuming CURRENT_DATE is disallowed in views
• Thinking views store data needing refresh
• Blaming INTERVAL syntax without checking error message

5. You want to restrict users to see only active employees' names and departments without exposing salaries. Which approach using views is best?

hard

A. Create a view selecting name, department, and salary for all employees

B. Create a view selecting all columns but filter status = 'active'

C. Create a view selecting only salary and status columns

D. Create a view selecting only name and department from employees where status = 'active'

Solution

1. Step 1: Identify data to expose

   Only active employees' names and departments should be visible, no salaries.

2. Step 2: Choose view that filters and limits columns

   Create a view selecting only name and department from employees where status = 'active' selects only needed columns and filters active status, protecting salary data.

3. Final Answer:

   Create a view selecting only name and department from employees where status = 'active' -> Option D

4. Quick Check:

   View limits columns and filters rows = C [OK]

Hint: Select only needed columns and filter rows in view [OK]

Common Mistakes:

• Including salary column exposing sensitive data
• Not filtering active status
• Selecting all columns unnecessarily