Presence validation in Ruby on Rails - Performance & Optimization

Performance: Presence validation

MEDIUM IMPACT

Presence validation affects server-side response time and user experience by preventing unnecessary database writes and reducing error handling on the client.

Ensuring a form field is not empty before saving data

Ruby on Rails

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

# In controller
user = User.new(params[:user])
if user.save
  # success
else
  # handle validation errors
end

Prevents saving invalid data, reducing unnecessary database operations and improving response speed.

📈 Performance GainReduces server load and improves interaction responsiveness (better INP).

Ensuring a form field is not empty before saving data

Ruby on Rails

class User < ApplicationRecord
  # No presence validation
end

# In controller
user = User.new(params[:user])
user.save # saves even if fields are empty

Allows empty fields to be saved, causing extra database writes and later error handling.

📉 Performance CostIncreases server processing and database load, slowing response time.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No presence validation	N/A (server-side)	N/A	N/A	[X] Bad
With presence validation	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

Presence validation runs on the server before database operations, preventing invalid data from triggering costly database writes and subsequent error rendering.

→Server Processing

→Database Write

→Response Rendering

⚠️ BottleneckDatabase Write stage is most expensive if invalid data is saved.

Core Web Vital Affected

INP

Presence validation affects server-side response time and user experience by preventing unnecessary database writes and reducing error handling on the client.

Optimization Tips

1Always validate presence before saving to reduce server load.

2Presence validation improves interaction responsiveness (INP).

3Skipping presence validation causes unnecessary database writes and slower responses.

Performance Quiz - 3 Questions

How does presence validation affect server performance?

A It increases database writes by allowing empty data.

B It reduces unnecessary database writes by blocking invalid data early.

C It has no effect on server performance.

D It slows down the server by adding extra processing.

DevTools: Network

How to check: Open DevTools, go to Network tab, submit form with empty required fields, observe server response time and error messages.

What to look for: Faster server response with validation errors returned immediately indicates good presence validation.

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