Schemas for namespace organization in PostgreSQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a schema in PostgreSQL?

A schema is a way to organize database objects like tables and views into separate namespaces, helping avoid name conflicts and grouping related objects.

beginner

How does a schema help with namespace organization?

Schemas create separate containers for objects, so two tables with the same name can exist in different schemas without conflict.

beginner

How do you create a new schema in PostgreSQL?

Use the command CREATE SCHEMA schema_name; to create a new schema.

beginner

How do you refer to a table inside a specific schema?

Use schema_name.table_name to specify the schema and table, like sales.customers.

beginner

What is the default schema in PostgreSQL if none is specified?

The default schema is public. If you don’t specify a schema, PostgreSQL looks in public.

What does a schema in PostgreSQL help organize?

A Operating system files

B Only user accounts

C Database objects like tables and views

D Network connections

Schemas organize database objects such as tables and views into namespaces.

Which command creates a new schema named 'inventory'?

A CREATE TABLE inventory;

B MAKE SCHEMA inventory;

C NEW SCHEMA inventory;

D CREATE SCHEMA inventory;

The correct syntax to create a schema is CREATE SCHEMA followed by the schema name.

How do you refer to a table named 'orders' inside the 'sales' schema?

A sales.orders

B orders.sales

C orders:sales

D sales-orders

The correct format is schema_name.table_name, so sales.orders.

What is the default schema in PostgreSQL?

A default

B public

C system

D main

PostgreSQL uses the public schema by default if no schema is specified.

Why use schemas in a database?

A To organize objects and avoid name conflicts

B To store backups

C To speed up queries

D To encrypt data

Schemas help organize database objects and prevent name conflicts by grouping objects into namespaces.

Explain what a schema is and how it helps organize database objects in PostgreSQL.

Think about how folders organize files on your computer.

Describe how to create a schema and how to reference a table inside that schema.

Remember the syntax for creating and using 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