Why Presence validation in Ruby on Rails? - Purpose & Use Cases

The Big Idea

Discover how a simple validation saves you from countless bugs and headaches!

The Scenario

Imagine building a sign-up form where users must enter their email and password. You try to check manually if these fields are empty by writing extra code everywhere before saving data.

The Problem

Manually checking each field every time is tiring and easy to forget. This leads to bugs where empty or incomplete data sneaks into your database, causing errors later.

The Solution

Presence validation in Rails automatically checks if required fields are filled before saving. It keeps your data clean without extra repetitive code.

Before vs After

✗ Before

if params[:email].blank? || params[:password].blank?
  render 'error'
else
  save_user(params)
end

✓ After

validates :email, presence: true
validates :password, presence: true

What It Enables

It lets you trust your data is complete and focus on building features, not on tedious checks.

Real Life Example

When users sign up on a website, presence validation ensures they don't leave important fields blank, preventing account creation errors.

Key Takeaways

Manual checks for empty fields are repetitive and error-prone.

Presence validation automates these checks in Rails models.

This keeps data reliable and your code cleaner.

Practice

1. What does validates :name, presence: true do in a Rails model?

easy

A. It ensures the name field is not empty before saving.

B. It automatically fills the name field with a default value.

C. It deletes the record if name is empty.

D. It allows name to be empty without errors.

Solution

1. Step 1: Understand presence validation purpose

   Presence validation checks that a field is not blank before saving a record.

2. Step 2: Apply to name field

   Using validates :name, presence: true means the name must have a value.

3. Final Answer:

   It ensures the name field is not empty before saving. -> Option A

4. Quick Check:

   Presence validation = field not empty [OK]

Hint: Presence validation means field cannot be blank [OK]

Common Mistakes:

• Thinking it fills default values automatically
• Confusing presence with uniqueness validation
• Assuming it deletes records if empty

2. Which of the following is the correct syntax to add presence validation for the email attribute in a Rails model?

easy

A. validates_presence_of email

B. validates :email, presence: true

C. validate :email, presence: true

D. validates :email, required: true

Solution

1. Step 1: Recall modern Rails validation syntax

   Rails uses validates :attribute, presence: true for presence validation.

2. Step 2: Check each option

   validates_presence_of email is invalid syntax (missing symbol ":email"); validates :email, presence: true is the correct modern syntax; validate :email, presence: true is incorrect method name; validates :email, required: true uses wrong option key.

3. Final Answer:

   validates :email, presence: true -> Option B

4. Quick Check:

   Use validates :field, presence: true [OK]

Hint: Use validates :field, presence: true for presence [OK]

Common Mistakes:

• Using validate instead of validates
• Using required instead of presence
• Confusing old and new syntax

3. Given this model code:

class User < ApplicationRecord
  validates :username, presence: true
end

What happens if you try to save User.new(username: '')?

medium

A. The save fails because username is blank.

B. The user is saved with an empty username.

C. An error is raised due to syntax error.

D. The username is automatically set to 'default'.

Solution

1. Step 1: Understand presence validation effect on blank string

   Presence validation treats empty strings as invalid, so saving fails.

2. Step 2: Apply to username: ''

   Since username is empty string, validation fails and save returns false.

3. Final Answer:

   The save fails because username is blank. -> Option A

4. Quick Check:

   Empty string fails presence validation [OK]

Hint: Empty string fails presence validation, save returns false [OK]

Common Mistakes:

• Thinking empty string passes presence validation
• Expecting automatic default value assignment
• Confusing validation failure with exceptions

4. Identify the error in this model validation code:

class Product < ApplicationRecord
  validates :title, presence
end

medium

A. No error, code is correct.

B. Should use validate instead of validates.

C. The attribute title must be a string.

D. Missing true after presence.

Solution

1. Step 1: Check presence validation syntax

   Presence validation requires presence: true, not just presence.

2. Step 2: Identify missing true

   The code misses : true after presence, causing syntax error.

3. Final Answer:

   Missing true after presence. -> Option D

4. Quick Check:

   Presence validation needs presence: true [OK]

Hint: Always write presence: true for presence validation [OK]

Common Mistakes:

• Omitting : true after presence
• Using validate instead of validates
• Assuming attribute type affects validation syntax

5. You want to ensure a Post model's title and content are present, but content can be blank if title is 'Draft'. Which validation setup achieves this?

hard

A. validates :title, presence: true
validates :content, presence: false, unless: -> { title == 'Draft' }

B. validates :title, presence: true
validates :content, presence: true, if: -> { title == 'Draft' }

C. validates :title, presence: true
validates :content, presence: true, unless: -> { title == 'Draft' }

D. validates :title, presence: true
validates :content, presence: false, if: -> { title == 'Draft' }

Solution

1. Step 1: Understand requirement for content

   Content must be present except when title is 'Draft'.

2. Step 2: Use conditional presence validation

   Use presence: true with unless condition to skip validation if title is 'Draft'.

3. Step 3: Check options

   validates :title, presence: true validates :content, presence: true, unless: -> { title == 'Draft' } correctly uses unless: -> { title == 'Draft' } to skip content presence validation when title is 'Draft'. Others misuse if or set presence false incorrectly.

4. Final Answer:

   validates :title, presence: true validates :content, presence: true, unless: -> { title == 'Draft' } -> Option C

5. Quick Check:

   Use unless to skip presence validation conditionally [OK]

Hint: Use unless to skip presence validation conditionally [OK]

Common Mistakes:

• Using if instead of unless for skipping validation
• Setting presence: false which disables validation
• Not combining validations properly