Schemas for namespace organization in PostgreSQL - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ query_result

intermediate

Querying tables in different schemas

Consider two schemas sales and hr in a PostgreSQL database. Each schema has a table named employees. What will the following query return?

SELECT * FROM sales.employees;

A All rows from the employees table in the sales schema

B All rows from the employees table in the hr schema

C All rows from employees tables in both sales and hr schemas combined

D An error because employees table exists in multiple schemas

💡 Hint

Think about how schema-qualified names work in PostgreSQL.

When you specify a schema name before a table, PostgreSQL queries that specific table only. So sales.employees refers to the employees table inside the sales schema.

🧠 Conceptual

intermediate

Purpose of schemas in PostgreSQL

What is the main purpose of using schemas in PostgreSQL?

A To improve query performance by indexing tables automatically

B To encrypt data stored in tables

C To organize database objects into separate namespaces to avoid name conflicts

D To automatically backup tables daily

💡 Hint

Think about why you might want to have multiple tables with the same name in one database.

Schemas allow grouping tables and other objects into separate namespaces. This helps avoid name clashes and organize objects logically.

📝 Syntax

advanced

Creating a schema and setting search path

Which of the following commands correctly creates a schema named marketing and sets it as the first schema in the search path?

A CREATE SCHEMA marketing; SET search_path TO marketing, public;

B CREATE SCHEMA marketing; SET search_path = marketing, public;

C CREATE SCHEMA marketing; SET search_path TO public, marketing;

D CREATE SCHEMA marketing; SET search_path = public, marketing;

💡 Hint

Remember the syntax for setting the search path and the order of schemas matters.

The command SET search_path TO marketing, public; sets the search path so that PostgreSQL looks first in the marketing schema, then public. The keyword TO is correct syntax.

❓ optimization

advanced

Optimizing schema usage for large databases

You have a large database with many tables. How can using schemas help optimize database management and queries?

A Schemas automatically partition tables to improve query speed

B By grouping related tables into schemas, you can manage permissions and backups more efficiently

C Schemas compress data to reduce storage size

D Schemas replicate tables across servers for load balancing

💡 Hint

Think about administrative tasks and security.

Schemas help organize tables logically, making it easier to assign permissions and manage backups per group. They do not automatically partition or compress data.

🔧 Debug

expert

Resolving ambiguous table reference error

You run the query SELECT * FROM employees; but get an error saying the table reference is ambiguous. You have two schemas, sales and hr, each with an employees table. How can you fix this error?

A Set the search_path to only one schema containing employees table

B Rename one of the employees tables to a different name

C Drop one of the employees tables

D Specify the schema explicitly in the query, e.g., <code>SELECT * FROM sales.employees;</code>

💡 Hint

Think about how to tell PostgreSQL exactly which table you want.

Explicitly specifying the schema removes ambiguity. Renaming or dropping tables is not always practical. Setting search_path might help but can still cause ambiguity if both schemas are in the path.

Practice

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

easy

A. To group database objects and avoid name conflicts

B. To speed up query execution automatically

C. To store backup copies of tables

D. To encrypt data in the database

Solution

1. Step 1: Understand what schemas do

   Schemas act like folders in a database to group tables and other objects.

2. Step 2: Identify the main benefit

   Grouping objects helps avoid name conflicts when different parts use the same table names.

3. Final Answer:

   To group database objects and avoid name conflicts -> Option A

4. Quick Check:

   Schemas = Group objects + avoid conflicts [OK]

Hint: Schemas are like folders to organize database objects [OK]

Common Mistakes:

• Thinking schemas speed up queries automatically
• Confusing schemas with backups
• Assuming schemas encrypt data

2. Which of the following is the correct syntax to create a new schema named sales in PostgreSQL?

easy

A. NEW SCHEMA sales;

B. MAKE SCHEMA sales;

C. CREATE SCHEMA sales;

D. CREATE DATABASE sales;

Solution

1. Step 1: Recall the command to create schemas

   The correct command to create a schema is CREATE SCHEMA schema_name;.

2. Step 2: Match the syntax with options

   Only CREATE SCHEMA sales; uses the correct syntax: CREATE SCHEMA sales;.

3. Final Answer:

   CREATE SCHEMA sales; -> Option C

4. Quick Check:

   CREATE SCHEMA = create schema [OK]

Hint: Use CREATE SCHEMA to make a new schema [OK]

Common Mistakes:

• Using MAKE or NEW instead of CREATE
• Confusing CREATE SCHEMA with CREATE DATABASE
• Missing the semicolon at the end

3. Given the following commands:

CREATE SCHEMA hr;
CREATE TABLE hr.employees (id INT, name TEXT);
SET search_path TO hr;
SELECT * FROM employees;

What will the SELECT query return?

medium

A. Error: table employees does not exist

B. Empty result set

C. All rows from the public.employees table

D. All rows from the hr.employees table

Solution

1. Step 1: Understand schema and search_path

   The table employees is created inside the hr schema. Setting search_path to hr tells PostgreSQL to look in hr first for tables.

2. Step 2: What does SELECT * FROM employees do?

   Since search_path is set to hr, the query finds hr.employees and returns its rows.

3. Final Answer:

   All rows from the hr.employees table -> Option D

4. Quick Check:

   search_path = hr, so employees = hr.employees [OK]

Hint: SET search_path to schema to query its tables without schema prefix [OK]

Common Mistakes:

• Assuming employees table is in public schema
• Forgetting to set search_path
• Expecting an error because of missing schema prefix

4. You run the following commands:

CREATE SCHEMA finance;
CREATE TABLE finance.budget (id INT, amount NUMERIC);
SELECT * FROM budget;

The last SELECT query gives an error. What is the most likely cause?

medium

A. The table budget has no columns

B. The table budget does not exist in the current search_path

C. The CREATE TABLE command failed silently

D. You need to use DROP SCHEMA before creating tables

Solution

1. Step 1: Check where the table was created

   The table budget was created inside the finance schema, not the default public schema.

2. Step 2: Understand why SELECT fails

   Without setting search_path to finance, PostgreSQL looks in public by default and does not find budget.

3. Final Answer:

   The table budget does not exist in the current search_path -> Option B

4. Quick Check:

   Table in finance schema, search_path missing = error [OK]

Hint: Set search_path or use schema.table to avoid missing table errors [OK]

Common Mistakes:

• Assuming table exists in public schema automatically
• Thinking CREATE TABLE silently fails
• Confusing DROP SCHEMA with table creation

5. You want to organize tables for two projects, alpha and beta, in the same PostgreSQL database. Which approach best uses schemas to avoid name conflicts and keep data organized?

hard

A. Create schemas alpha and beta, then create tables inside each schema

B. Create tables with prefixes like alpha_ and beta_ in the public schema

C. Create separate databases for each project

D. Use one schema and name tables uniquely without prefixes

Solution

1. Step 1: Understand schema use for organization

   Schemas group objects logically and avoid name conflicts by namespace separation.

2. Step 2: Compare options for organizing projects

   Creating separate schemas for alpha and beta keeps tables organized and allows same table names in each schema.

3. Final Answer:

   Create schemas alpha and beta, then create tables inside each schema -> Option A

4. Quick Check:

   Schemas = separate namespaces for projects [OK]

Hint: Use separate schemas per project to avoid name conflicts [OK]

Common Mistakes:

• Using prefixes instead of schemas
• Creating separate databases unnecessarily
• Putting all tables in one schema without clear naming