Why date handling matters in PostgreSQL - See It in Action

Why date handling matters in PostgreSQL

📖 Scenario: You are managing a small library database. You need to store book borrowing dates and calculate due dates correctly. Handling dates properly is important to avoid errors like overdue books or wrong return dates.

🎯 Goal: Build a simple PostgreSQL table to store book borrowings with correct date columns, add a configuration for loan period, calculate due dates using date arithmetic, and finalize the table with constraints to ensure date validity.

📋 What You'll Learn

Create a table named borrowings with columns book_id (integer) and borrow_date (date)

Add a configuration variable loan_period_days to set the loan duration in days

Write a query to select book_id, borrow_date, and calculate due_date by adding loan_period_days to borrow_date

Add a constraint to ensure borrow_date is not in the future

💡 Why This Matters

🌍 Real World

Libraries, rental services, and any system tracking borrowed items need accurate date handling to manage due dates and avoid errors.

💼 Career

Database developers and administrators must handle dates correctly to ensure data integrity and support business rules involving time.

1

Create the borrowings table

Create a table called borrowings with two columns: book_id as integer and borrow_date as date.

PostgreSQL

-- Your code here to create the borrowings table

Hint

Use CREATE TABLE statement with the specified columns and types.

2

Add loan period configuration

Create a variable called loan_period_days and set it to 14 to represent a 14-day loan period.

PostgreSQL

CREATE TABLE borrowings (
    book_id INTEGER,
    borrow_date DATE
);
-- Your code here to set loan_period_days

Hint

Use the \set command in psql to define a variable.

3

Calculate due dates

Write a SELECT query to get book_id, borrow_date, and calculate due_date by adding loan_period_days days to borrow_date. Use the variable loan_period_days in the query.

PostgreSQL

CREATE TABLE borrowings (
    book_id INTEGER,
    borrow_date DATE
);

\set loan_period_days 14

-- Your code here to select book_id, borrow_date, and due_date

Hint

Use INTERVAL with the variable :loan_period_days to add days.

4

Add constraint for borrow_date

Alter the borrowings table to add a CHECK constraint named borrow_date_not_future that ensures borrow_date is less than or equal to the current date (CURRENT_DATE).

PostgreSQL

CREATE TABLE borrowings (
    book_id INTEGER,
    borrow_date DATE
);

\set loan_period_days 14

SELECT book_id, borrow_date, borrow_date + (:loan_period_days || ' days')::interval AS due_date
FROM borrowings;

-- Your code here to add the CHECK constraint

Hint

Use ALTER TABLE with ADD CONSTRAINT and a CHECK condition.

Practice

1. Why is it important to use the DATE or TIMESTAMP types in PostgreSQL when working with dates?

easy

A. They automatically convert dates to strings for display.

B. They store dates as plain text for easy editing.

C. They allow accurate sorting and filtering of data by time.

D. They prevent any date values from being stored.

Solution

1. Step 1: Understand date types purpose

   DATE and TIMESTAMP types store date and time in a format PostgreSQL can understand and compare.

2. Step 2: Recognize benefits for sorting and filtering

   Using these types allows PostgreSQL to sort and filter data accurately by date/time values.

3. Final Answer:

   They allow accurate sorting and filtering of data by time. -> Option C

4. Quick Check:

   Date types enable correct time-based queries [OK]

Hint: Use DATE/TIMESTAMP to sort/filter dates correctly [OK]

Common Mistakes:

• Treating dates as plain text causes wrong sorting
• Assuming dates auto-convert to strings for display
• Ignoring the difference between DATE and TIMESTAMP

2. Which of the following is the correct way to declare a column named created_at that stores date and time in PostgreSQL?

easy

A. created_at TIMESTAMP

B. created_at DATE

C. created_at INT

D. created_at VARCHAR(20)

Solution

1. Step 1: Identify the data type for date and time

   To store both date and time, PostgreSQL uses the TIMESTAMP type.

2. Step 2: Compare options

   VARCHAR stores text, DATE stores only date without time, INT stores numbers, so TIMESTAMP is correct.

3. Final Answer:

   created_at TIMESTAMP -> Option A

4. Quick Check:

   Use TIMESTAMP for date and time columns [OK]

Hint: Use TIMESTAMP for date and time columns [OK]

Common Mistakes:

• Using VARCHAR instead of date/time types
• Using DATE when time is needed
• Using INT for date storage

3. Given the table events(event_name TEXT, event_date DATE), what will this query return?

SELECT event_name FROM events WHERE event_date > '2024-01-01';

medium

A. All events after January 1, 2024

B. All events on or before January 1, 2024

C. All events on January 1, 2024

D. Syntax error due to date format

Solution

1. Step 1: Understand the WHERE clause condition

   The condition event_date > '2024-01-01' filters events with dates strictly after January 1, 2024.

2. Step 2: Interpret the query result

   The query returns event names where event_date is greater than January 1, 2024, excluding that date itself.

3. Final Answer:

   All events after January 1, 2024 -> Option A

4. Quick Check:

   event_date > '2024-01-01' means dates after that day [OK]

Hint: Remember > excludes the date itself [OK]

Common Mistakes:

• Confusing > with >= operator
• Thinking the date format causes errors
• Assuming it includes the date '2024-01-01'

4. You wrote this query to find events on March 15, 2024:

SELECT * FROM events WHERE event_date = '15-03-2024';

But it returns no rows. What is the likely problem?

medium

A. The event_date column is not indexed.

B. The date format '15-03-2024' is not recognized by PostgreSQL.

C. The table name is incorrect.

D. The query needs a TIMESTAMP instead of DATE.

Solution

1. Step 1: Check date format used in query

   PostgreSQL expects dates in 'YYYY-MM-DD' format by default, not 'DD-MM-YYYY'.

2. Step 2: Understand why no rows returned

   Because '15-03-2024' is not recognized as a valid date, the condition matches no rows.

3. Final Answer:

   The date format '15-03-2024' is not recognized by PostgreSQL. -> Option B

4. Quick Check:

   Use 'YYYY-MM-DD' format for dates [OK]

Hint: Use ISO date format YYYY-MM-DD [OK]

Common Mistakes:

• Using DD-MM-YYYY instead of YYYY-MM-DD
• Assuming PostgreSQL auto-converts date formats
• Blaming indexing or table name for no results

5. You want to find all events that happened in the year 2023 using the events(event_date DATE) table. Which query correctly returns these events?

hard

A. SELECT * FROM events WHERE event_date BETWEEN '2023-01-01' AND '2023-12-31';

B. SELECT * FROM events WHERE EXTRACT(YEAR FROM event_date) = 2023;

C. SELECT * FROM events WHERE event_date >= '2023-01-01' AND event_date < '2024-01-01';

D. All of the above

Solution

1. Step 1: Analyze SELECT * FROM events WHERE event_date BETWEEN '2023-01-01' AND '2023-12-31';

   Using BETWEEN with '2023-01-01' and '2023-12-31' includes all dates in 2023.

2. Step 2: Analyze SELECT * FROM events WHERE EXTRACT(YEAR FROM event_date) = 2023;

   EXTRACT(YEAR FROM event_date) = 2023 filters events in 2023 by extracting the year part.

3. Step 3: Analyze SELECT * FROM events WHERE event_date >= '2023-01-01' AND event_date < '2024-01-01';

   Using >= '2023-01-01' and < '2024-01-01' also correctly selects all 2023 dates.

4. Final Answer:

   All of the above -> Option D

5. Quick Check:

   Multiple correct ways to filter by year [OK]

Hint: Use BETWEEN, EXTRACT, or range for year filtering [OK]

Common Mistakes:

• Using incorrect date ranges that exclude some days
• Forgetting to use < '2024-01-01' for inclusive year end
• Assuming only one method works for year filtering