Why Boolean type behavior in PostgreSQL? - Purpose & Use Cases

The Big Idea

Discover how a simple true or false can save you hours of confusion and mistakes!

The Scenario

Imagine you have a list of tasks written on paper, and you mark each as done or not done by writing 'yes' or 'no'. When you want to find all done tasks, you have to read each note carefully and interpret the words.

The Problem

This manual way is slow and confusing because words like 'yes', 'no', 'done', or 'not done' can be written differently or misunderstood. It's easy to make mistakes and hard to quickly find what you want.

The Solution

Using a Boolean type means storing only two clear values: true or false. This makes checking conditions fast and reliable, like flipping a simple switch instead of guessing from words.

Before vs After

✗ Before

SELECT * FROM tasks WHERE status = 'done' OR status = 'yes';

✓ After

SELECT * FROM tasks WHERE is_done = TRUE;

What It Enables

It enables quick, error-free filtering and decision-making by using simple true/false values in your database.

Real Life Example

For example, an online store can quickly find all orders that have been shipped by checking a Boolean 'shipped' field instead of searching through messy text descriptions.

Key Takeaways

Manual text flags are confusing and error-prone.

Boolean type stores clear true/false values.

This makes queries faster and more reliable.

Practice

1. In PostgreSQL, which of the following is a valid boolean value stored in a boolean column?

easy

A. TRUE

B. 2

C. 'foo'

D. 'NULL'

Solution

1. Step 1: Understand boolean data type values

   PostgreSQL boolean columns accept TRUE, FALSE, or NULL (unknown).

2. Step 2: Identify valid boolean literals

   TRUE and FALSE are valid boolean literals; 2, 'foo', and 'NULL' are not valid boolean literals in PostgreSQL.

3. Final Answer:

   TRUE -> Option A

4. Quick Check:

   Boolean values = TRUE or FALSE [OK]

Hint: Boolean columns accept TRUE, FALSE, or NULL only [OK]

Common Mistakes:

• Using 1 or 0 as boolean values directly
• Using strings like 'yes' or 'no' as boolean
• Confusing NULL with a boolean TRUE or FALSE

2. Which of the following is the correct way to declare a boolean column named is_active in a PostgreSQL table?

easy

A. CREATE TABLE users (is_active BOOLEAN(1));

B. CREATE TABLE users (is_active BOOLEAN);

C. CREATE TABLE users (is_active BOOL(1));

D. CREATE TABLE users (is_active BOOLIAN);

Solution

1. Step 1: Check correct boolean type syntax

   PostgreSQL uses BOOLEAN or BOOL as valid types; BOOLEAN(1) is invalid.

2. Step 2: Identify syntax errors

   A uses invalid BOOLEAN(1) syntax; B has a typo 'BOOLIAN'; C uses invalid BOOL(1) syntax.

3. Final Answer:

   CREATE TABLE users (is_active BOOLEAN); -> Option B

4. Quick Check:

   BOOLEAN keyword is correct type [OK]

Hint: Use BOOLEAN or BOOL, no size or typo allowed [OK]

Common Mistakes:

• Typo in BOOLEAN keyword
• Adding size like BOOLEAN(1)
• Using unsupported types like BOOLIAN

3. Given the table settings with a boolean column enabled, what will this query return?

SELECT enabled FROM settings WHERE enabled = FALSE;

medium

A. All rows where enabled is TRUE

B. All rows where enabled is NULL

C. All rows where enabled is FALSE

D. Syntax error

Solution

1. Step 1: Understand the WHERE clause condition

   The query filters rows where the boolean column enabled equals FALSE.

2. Step 2: Determine which rows match

   Only rows with enabled = FALSE will be returned; TRUE or NULL rows are excluded.

3. Final Answer:

   All rows where enabled is FALSE -> Option C

4. Quick Check:

   WHERE enabled = FALSE returns FALSE rows [OK]

Hint: WHERE boolean_column = FALSE returns only FALSE rows [OK]

Common Mistakes:

• Assuming NULL rows are included
• Confusing TRUE and FALSE values
• Thinking it returns all rows

4. You wrote this query but it returns no rows:

SELECT * FROM users WHERE is_admin = TRUE;

The is_admin column is boolean but some rows have NULL. What is the likely issue?

medium

A. TRUE is not a valid boolean value in PostgreSQL

B. The query syntax is incorrect

C. The column should be text, not boolean

D. NULL values cause the condition to fail, so no rows with NULL appear

Solution

1. Step 1: Understand boolean NULL behavior in WHERE clause

   Comparing boolean column to TRUE excludes NULL rows because NULL means unknown, not TRUE.

2. Step 2: Explain why no rows returned

   Rows with NULL in is_admin do not satisfy is_admin = TRUE, so they are excluded.

3. Final Answer:

   NULL values cause the condition to fail, so no rows with NULL appear -> Option D

4. Quick Check:

   NULL in boolean = TRUE returns no rows [OK]

Hint: NULL in boolean columns excludes rows in equality checks [OK]

Common Mistakes:

• Thinking NULL equals TRUE
• Assuming TRUE is invalid boolean
• Believing syntax error caused no rows

5. You want to select all rows from tasks where the boolean column completed is either FALSE or NULL. Which query correctly does this?

hard

A. SELECT * FROM tasks WHERE completed = FALSE OR completed IS NULL;

B. SELECT * FROM tasks WHERE completed = FALSE AND completed IS NULL;

C. SELECT * FROM tasks WHERE NOT completed;

D. SELECT * FROM tasks WHERE completed != TRUE;

Solution

1. Step 1: Understand boolean NULL and FALSE filtering

   To get rows where completed is FALSE or NULL, use OR with completed = FALSE and completed IS NULL.

2. Step 2: Analyze each option

   SELECT * FROM tasks WHERE completed = FALSE AND completed IS NULL; uses AND, which cannot be both FALSE and NULL simultaneously. SELECT * FROM tasks WHERE NOT completed; excludes NULL rows. SELECT * FROM tasks WHERE completed != TRUE; excludes TRUE and NULL (since NULL != TRUE is unknown), includes only FALSE.

3. Final Answer:

   SELECT * FROM tasks WHERE completed = FALSE OR completed IS NULL; -> Option A

4. Quick Check:

   Use OR to include FALSE or NULL rows [OK]

Hint: Use OR with IS NULL to include unknown boolean values [OK]

Common Mistakes:

• Using AND instead of OR
• Ignoring NULL rows in boolean filters
• Using NOT completed excludes NULL rows