Schemas for namespace organization in PostgreSQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new schema named 'sales'.

PostgreSQL

CREATE SCHEMA [1];

Drag options to blanks, or click blank then click option'

Asales

Bdatabase

Ctable

Dpublic

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'database' or 'table' instead of a schema name.

Trying to create a schema without a name.

The CREATE SCHEMA command followed by the schema name creates a new schema. Here, 'sales' is the schema name.

2fill in blank

medium

Complete the code to set the search path to the 'sales' schema.

PostgreSQL

SET search_path TO [1];

Drag options to blanks, or click blank then click option'

Apublic

Bsales

Cmain

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'public' when the goal is to use 'sales'.

Using invalid schema names.

The SET search_path TO command changes the schema search order. Setting it to 'sales' makes that schema the default for object lookups.

3fill in blank

hard

Fix the error in the code to create a table named 'orders' inside the 'sales' schema.

PostgreSQL

CREATE TABLE [1].orders (id SERIAL PRIMARY KEY, amount NUMERIC);

Drag options to blanks, or click blank then click option'

Apublic

Bdefault

Cmain

Dsales

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the schema name and creating the table in the default schema.

Using a schema name that does not exist.

To create a table inside a specific schema, prefix the table name with the schema name and a dot. Here, 'sales.orders' creates the table in the 'sales' schema.

4fill in blank

hard

Fill both blanks to query all rows from the 'orders' table in the 'sales' schema.

PostgreSQL

SELECT * FROM [1].[2];

Drag options to blanks, or click blank then click option'

Asales

Borders

Cpublic

Dcustomers

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping schema and table names.

Using the wrong schema or table name.

To query a table in a specific schema, use schema_name.table_name. Here, 'sales.orders' selects from the 'orders' table in the 'sales' schema.

5fill in blank

hard

Fill all three blanks to grant SELECT permission on the 'orders' table in the 'sales' schema to user 'analyst'.

PostgreSQL

GRANT [1] ON [2].[3] TO analyst;

Drag options to blanks, or click blank then click option'

ASELECT

Bsales

Corders

DUPDATE

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong permission like UPDATE instead of SELECT.

Mixing up schema and table names.

The GRANT SELECT ON schema.table TO user command gives read permission on the table. Here, 'SELECT' is the permission, 'sales' is the schema, and 'orders' is the table.

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