Schemas for namespace organization in PostgreSQL - Mini Project: Build & Apply

Schemas for Namespace Organization in PostgreSQL

📖 Scenario: You are managing a small company's database. To keep things tidy, you want to organize tables into different schemas based on departments.

🎯 Goal: Create schemas to organize tables by department and create tables inside those schemas.

📋 What You'll Learn

Create two schemas named sales and hr

Create a table named customers inside the sales schema with columns id (integer) and name (text)

Create a table named employees inside the hr schema with columns id (integer) and fullname (text)

Set the search path to include sales and hr schemas

💡 Why This Matters

🌍 Real World

Organizing database objects into schemas helps large applications keep data structured and avoid name conflicts.

💼 Career

Database administrators and developers use schemas to manage complex databases efficiently and maintain clear separation of data.

1

Create schemas for departments

Write SQL statements to create two schemas named sales and hr.

PostgreSQL

-- Your code here to create schemas sales and hr

Hint

Use CREATE SCHEMA schema_name; to create a schema.

2

Create tables inside schemas

Create a table named customers inside the sales schema with columns id (integer) and name (text). Also create a table named employees inside the hr schema with columns id (integer) and fullname (text).

PostgreSQL

CREATE SCHEMA sales;
CREATE SCHEMA hr;
-- Your code here to create tables customers and employees inside schemas

Hint

Use CREATE TABLE schema_name.table_name (columns); to create tables inside schemas.

3

Set the search path

Write a SQL statement to set the search path to include the sales and hr schemas in that order.

PostgreSQL

CREATE SCHEMA sales;
CREATE SCHEMA hr;

CREATE TABLE sales.customers (
    id INTEGER,
    name TEXT
);

CREATE TABLE hr.employees (
    id INTEGER,
    fullname TEXT
);

-- Your code here to set search path

Hint

Use SET search_path TO schema1, schema2; to set the search path.

4

Verify table creation with schema prefix

Write SQL statements to select all columns from customers table in the sales schema and from employees table in the hr schema using schema-qualified names.

PostgreSQL

CREATE SCHEMA sales;
CREATE SCHEMA hr;

CREATE TABLE sales.customers (
    id INTEGER,
    name TEXT
);

CREATE TABLE hr.employees (
    id INTEGER,
    fullname TEXT
);

SET search_path TO sales, hr;

-- Your code here to select all from sales.customers and hr.employees

Hint

Use SELECT * FROM schema_name.table_name; to query tables inside schemas.

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