Creating and switching schemas in PostgreSQL - Quick Revision & Summary

Recall & Review

beginner

What is a schema in PostgreSQL?

A schema is like a folder inside a database that holds tables and other objects. It helps organize data so you can keep things neat and separate.

beginner

How do you create a new schema named 'sales' in PostgreSQL?

Use the command: CREATE SCHEMA sales; This makes a new schema called 'sales' inside your database.

beginner

How can you switch to use a different schema in PostgreSQL?

You change the search path with: SET search_path TO schema_name; This tells PostgreSQL to look in that schema first when you run commands.

intermediate

What does the command SET search_path TO public, sales; do?

It tells PostgreSQL to look first in the 'public' schema, then in the 'sales' schema when searching for tables or other objects.

beginner

Why is using schemas helpful in a database?

Schemas help keep data organized, avoid name conflicts, and let different teams or projects work in the same database without mixing up their tables.

Which command creates a new schema called 'inventory'?

A MAKE SCHEMA inventory;

B NEW SCHEMA inventory;

C CREATE SCHEMA inventory;

D ADD SCHEMA inventory;

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

How do you tell PostgreSQL to look in the 'marketing' schema first when running queries?

A CHANGE schema TO marketing;

B USE marketing;

C SET schema TO marketing;

D SET search_path TO marketing;

You use SET search_path TO schema_name; to set the schema search order.

If you run SET search_path TO sales, public;, which schema is checked first?

A sales

B None

C Both at the same time

D public

The first schema listed in search_path is checked first.

What is the default schema in PostgreSQL if you don't change the search path?

A sales

B public

C default

D main

By default, PostgreSQL uses the 'public' schema.

Why might you want to create multiple schemas in one database?

A To organize tables by project or team

B To make the database slower

C To delete data faster

D To avoid using tables

Schemas help organize data and avoid name conflicts by grouping tables logically.

Explain how to create a new schema and switch to it in PostgreSQL.

Think about making a folder and then telling the database to look inside it first.

Describe why using schemas can be helpful when multiple teams share the same database.

Imagine different teams having their own folders to keep their files separate.

Practice

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

easy

A. To encrypt the database tables

B. To speed up query execution automatically

C. To create backups of the database

D. To group database objects and organize them logically

Solution

1. Step 1: Understand what schemas do

   Schemas help organize tables, views, and other objects into groups.

2. Step 2: Identify the main purpose

   This organization helps keep the database tidy and manageable.

3. Final Answer:

   To group database objects and organize them logically -> Option D

4. Quick Check:

   Schemas = Organize objects [OK]

Hint: Schemas group objects to keep your database tidy [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?

easy

A. NEW SCHEMA sales;

B. CREATE SCHEMA sales;

C. MAKE SCHEMA sales;

D. CREATE DATABASE sales;

Solution

1. Step 1: Recall the command to create schemas

   The correct SQL command is CREATE SCHEMA schema_name;.

2. Step 2: Match the syntax

   CREATE SCHEMA sales; matches this syntax exactly for schema sales.

3. Final Answer:

   CREATE SCHEMA sales; -> Option B

4. Quick Check:

   CREATE SCHEMA = create schema [OK]

Hint: Use CREATE SCHEMA followed by the schema name [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 marketing;
SET search_path TO marketing;
CREATE TABLE campaigns (id SERIAL PRIMARY KEY, name TEXT);

What schema will the table campaigns belong to?

medium

A. marketing

B. None, it will cause an error

C. default

D. public

Solution

1. Step 1: Understand SET search_path effect

   Setting search_path to marketing means new objects are created in that schema by default.

2. Step 2: Check where the table is created

   The CREATE TABLE campaigns command creates the table inside the current schema in search_path, which is marketing.

3. Final Answer:

   marketing -> Option A

4. Quick Check:

   SET search_path = schema for new objects [OK]

Hint: SET search_path sets default schema for new tables [OK]

Common Mistakes:

• Assuming tables go to public schema by default
• Thinking SET search_path only affects queries, not creation
• Believing this causes an error without schema prefix

4. You run the command SET search_path TO sales; but get an error: ERROR: schema "sales" does not exist. What is the most likely cause?

medium

A. The schema sales was not created before setting search_path

B. You need to use USE sales; instead

C. The database connection is closed

D. The table sales does not exist

Solution

1. Step 1: Understand error meaning

   The error says the schema sales does not exist, so PostgreSQL cannot set search_path to it.

2. Step 2: Identify cause

   This usually means the schema was never created with CREATE SCHEMA sales;.

3. Final Answer:

   The schema sales was not created before setting search_path -> Option A

4. Quick Check:

   SET search_path needs existing schema [OK]

Hint: Create schema before setting search_path to it [OK]

Common Mistakes:

• Using USE instead of SET search_path in PostgreSQL
• Confusing tables with schemas
• Ignoring the error and continuing

5. You have two schemas: public and archive. You want to query a table named orders in archive without typing the full name every time. Which command will let you switch your session to use archive schema first, then public?

hard

A. USE archive, public;

B. ALTER SCHEMA archive SET search_path;

C. SET search_path TO archive, public;

D. SET schema TO archive, public;

Solution

1. Step 1: Recall how to set search_path for multiple schemas

   PostgreSQL uses SET search_path TO schema1, schema2; to set schema priority.

2. Step 2: Identify correct syntax

   SET search_path TO archive, public; correctly sets archive first, then public.

3. Final Answer:

   SET search_path TO archive, public; -> Option C

4. Quick Check:

   SET search_path sets schema order [OK]

Hint: Use SET search_path with comma-separated schemas [OK]

Common Mistakes:

• Using USE instead of SET search_path
• Trying ALTER SCHEMA to set search_path
• Using SET schema instead of SET search_path