CREATE VIEW syntax in PostgreSQL - Time & Space Complexity

Time Complexity: CREATE VIEW syntax

O(n)

Understanding Time Complexity

When we create a view in a database, it acts like a saved query. Understanding how the time to get results grows helps us know how efficient our view is.

We want to see how the time to get data from a view changes as the data grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

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

This code creates a view that shows orders from the last 30 days.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Scanning the orders table rows to check the date condition.
• How many times: Once for each row in the orders table when the view is queried.

How Execution Grows With Input

As the number of orders grows, the database checks more rows to find those in the last 30 days.

Input Size (n)	Approx. Operations
10	About 10 row checks
100	About 100 row checks
1000	About 1000 row checks

Pattern observation: The work grows roughly in direct proportion to the number of rows in the orders table.

Final Time Complexity

Time Complexity: O(n)

This means the time to get results grows linearly with the number of rows in the table.

Common Mistake

[X] Wrong: "Creating a view makes the query run faster because it stores results."

[OK] Correct: A view just saves the query, it does not store data. The database runs the query each time you ask the view, so the time depends on the underlying data size.

Interview Connect

Understanding how views work and their time cost shows you know how databases handle saved queries, a useful skill for real projects and interviews.

Self-Check

"What if we added an index on the order_date column? How would the time complexity change?"

Practice

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

easy

A. To delete rows from a table

B. To save a SELECT query as a virtual table for easy reuse

C. To permanently store data in a new table

D. To create an index on a table column

Solution

1. Step 1: Understand what a view is

   A view is a virtual table that stores a SELECT query, not actual data.

2. Step 2: Identify the purpose of CREATE VIEW

   CREATE VIEW saves the SELECT query so you can reuse it easily without rewriting it.

3. Final Answer:

   To save a SELECT query as a virtual table for easy reuse -> Option B

4. Quick Check:

   CREATE VIEW = virtual table for queries [OK]

Hint: Views save SELECT queries as virtual tables [OK]

Common Mistakes:

• Thinking views store data permanently
• Confusing views with tables
• Using CREATE VIEW to delete data

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 view_name AS SELECT ... [OK]

Hint: Syntax is CREATE VIEW name AS SELECT ... [OK]

Common Mistakes:

• Swapping CREATE and VIEW keywords
• Omitting AS keyword
• Missing semicolon at the end

3. Given the table orders with columns order_id, customer_id, and amount, what will be the result of this view?

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

What rows will SELECT * FROM big_orders; return?

medium

A. No rows, syntax error in view

B. All orders with amount less than or equal to 100

C. All orders regardless of amount

D. All orders with amount greater than 100

Solution

1. Step 1: Analyze the SELECT query inside the view

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

2. Step 2: Understand what SELECT * FROM big_orders returns

   It returns all rows from the view, which are orders with amount > 100.

3. Final Answer:

   All orders with amount greater than 100 -> Option D

4. Quick Check:

   View filters orders with amount > 100 [OK]

Hint: View returns rows matching its SELECT query condition [OK]

Common Mistakes:

• Confusing greater than with less than
• Expecting all columns instead of selected ones
• Assuming syntax error without checking carefully

4. Identify the error in this CREATE VIEW statement:

CREATE VIEW recent_customers AS SELECT id, name FROM customers WHERE;

medium

A. Missing condition after WHERE keyword

B. Missing AS keyword before SELECT

C. View name cannot be recent_customers

D. SELECT must include all columns

Solution

1. Step 1: Check the syntax after WHERE

   The WHERE clause is incomplete; it must have a condition after WHERE.

2. Step 2: Verify other parts of the statement

   AS keyword is present, view name is valid, and SELECT columns are allowed to be partial.

3. Final Answer:

   Missing condition after WHERE keyword -> Option A

4. Quick Check:

   WHERE must have a condition [OK]

Hint: WHERE clause must have a condition [OK]

Common Mistakes:

• Leaving WHERE empty
• Forgetting AS keyword
• Thinking view names have restrictions

5. You want to create a view customer_orders that shows each customer's name and the total amount they spent. Which of these is the correct way to create this view assuming tables customers(id, name) and orders(customer_id, amount)?

hard

A. CREATE VIEW customer_orders AS SELECT c.name, o.amount FROM customers c, orders o WHERE c.id = o.customer_id;

B. CREATE VIEW customer_orders AS SELECT name, amount FROM customers JOIN orders ON id = customer_id;

C. CREATE VIEW customer_orders AS SELECT c.name, SUM(o.amount) FROM customers c JOIN orders o ON c.id = o.customer_id GROUP BY c.name;

D. CREATE VIEW customer_orders AS SELECT name, SUM(amount) FROM orders GROUP BY name;

Solution

1. Step 1: Understand the requirement

   We need each customer's name and total amount spent, so we must join customers and orders and sum amounts grouped by customer name.

2. Step 2: Check each option

   CREATE VIEW customer_orders AS SELECT c.name, SUM(o.amount) FROM customers c JOIN orders o ON c.id = o.customer_id GROUP BY c.name; correctly joins tables, sums amounts, and groups by customer name. Others miss grouping or join conditions.

3. Final Answer:

   CREATE VIEW customer_orders AS SELECT c.name, SUM(o.amount) FROM customers c JOIN orders o ON c.id = o.customer_id GROUP BY c.name; -> Option C

4. Quick Check:

   Join + SUM + GROUP BY = correct view [OK]

Hint: Use JOIN with GROUP BY and SUM for aggregation views [OK]

Common Mistakes:

• Missing GROUP BY when using SUM
• Not joining tables properly
• Selecting columns not in GROUP BY