Why validations protect data integrity in Ruby on Rails - See It in Action

Why validations protect data integrity

📖 Scenario: You are building a simple Rails app to store user profiles. You want to make sure the data saved is correct and complete.

🎯 Goal: Learn how to add validations in a Rails model to protect data integrity by ensuring required fields are present and valid.

📋 What You'll Learn

Create a Rails model called User with attributes name and email

Add a validation to require name to be present

Add a validation to require email to be present and unique

Add a validation to ensure email has a valid email format

💡 Why This Matters

🌍 Real World

Validations prevent bad or incomplete data from being saved in databases, which helps apps work reliably and users trust the data.

💼 Career

Understanding validations is essential for backend developers working with Rails to build secure and robust applications.

1

Create the User model with attributes

Create a Rails model called User with attributes name:string and email:string.

Ruby on Rails

# Create the User model with name and email attributes
# Your code here

Hint

Use rails generate model User name:string email:string to create the model and migration.

2

Add presence validation for name

Add a validation in the User model to require the name attribute to be present.

Ruby on Rails

class User < ApplicationRecord
  # Add validation for presence of name
  # Your code here
end

Hint

Use validates :name, presence: true inside the model class.

3

Add presence and uniqueness validation for email

Add validations in the User model to require the email attribute to be present and unique.

Ruby on Rails

class User < ApplicationRecord
  validates :name, presence: true
  # Add validations for presence and uniqueness of email
  # Your code here
end

Hint

Use validates :email, presence: true, uniqueness: true inside the model class.

4

Add format validation for email

Add a validation in the User model to ensure the email attribute has a valid email format using a regular expression.

Ruby on Rails

class User < ApplicationRecord
  validates :name, presence: true
  validates :email, presence: true, uniqueness: true
  # Add format validation for email
  # Your code here
end

Hint

Use validates :email, format: { with: URI::MailTo::EMAIL_REGEXP } to check email format.

Practice

1. Why are validations important in a Rails application?

easy

A. They speed up the database queries automatically.

B. They generate user interface forms automatically.

C. They create database tables for the models.

D. They prevent invalid data from being saved to the database.

Solution

1. Step 1: Understand the role of validations

   Validations check data before saving to ensure it meets rules.

2. Step 2: Identify what validations protect

   They protect the database from bad or incorrect data entries.

3. Final Answer:

   They prevent invalid data from being saved to the database. -> Option D

4. Quick Check:

   Validations = prevent bad data [OK]

Hint: Validations stop bad data before saving [OK]

Common Mistakes:

• Thinking validations speed up queries
• Confusing validations with database migrations
• Assuming validations create UI forms

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

easy

A. validates :email, presence: true

B. validate :email, presence: true

C. validates_presence_of :email

D. validate_presence :email

Solution

1. Step 1: Recall Rails validation syntax

   The correct syntax uses validates with attribute and options.

2. Step 2: Match the correct method and option

   validates :email, presence: true is the modern and correct form.

3. Final Answer:

   validates :email, presence: true -> Option A

4. Quick Check:

   Use validates + attribute + option [OK]

Hint: Use 'validates' with attribute and presence: true [OK]

Common Mistakes:

• Using 'validate' instead of 'validates'
• Using deprecated 'validates_presence_of'
• Missing colon before attribute name

3. Given this model validation:

class User < ApplicationRecord
  validates :age, numericality: { greater_than_or_equal_to: 18 }
end

What happens if you try to save a user with age = 16?

medium

A. An error is raised and the app crashes.

B. The user is saved successfully with age 16.

C. The save fails because age is less than 18.

D. The age is automatically set to 18 and saved.

Solution

1. Step 1: Understand the numericality validation

   The validation requires age to be 18 or more to save.

2. Step 2: Check the given age value

   Age 16 is less than 18, so validation fails and save is blocked.

3. Final Answer:

   The save fails because age is less than 18. -> Option C

4. Quick Check:

   Age < 18 fails numericality validation [OK]

Hint: Validation blocks saving invalid data [OK]

Common Mistakes:

• Assuming invalid data saves anyway
• Thinking Rails auto-corrects invalid values
• Confusing validation failure with app crash

4. Look at this model code:

class Product < ApplicationRecord
  validates :name, presence: true
  validates :price, numericality: true
end

Why might saving Product.new(name: '', price: 'free') fail?

medium

A. Because Rails does not allow string prices.

B. Because name is empty and price is not a number.

C. Because validations are not defined correctly.

D. Because price is missing but name is valid.

Solution

1. Step 1: Check the presence validation on name

   Name is empty string, so presence validation fails.

2. Step 2: Check numericality validation on price

   Price is 'free' (a string), not a number, so numericality fails.

3. Final Answer:

   Because name is empty and price is not a number. -> Option B

4. Quick Check:

   Empty name + non-numeric price fail validations [OK]

Hint: Empty or wrong type values fail validations [OK]

Common Mistakes:

• Assuming empty string passes presence validation
• Thinking string 'free' counts as a number
• Believing validations auto-correct invalid data

5. You want to ensure a User model's username is unique and not empty. Which validation setup correctly protects data integrity?

hard

A. validates :username, presence: true, uniqueness: true

B. validates :username, presence: true; validates_uniqueness_of :username

C. validates_uniqueness_of :username, presence: true

D. validates :username, unique: true, presence: true

Solution

1. Step 1: Identify correct combined validation syntax

   Use validates with multiple options in one line for clarity.

2. Step 2: Check option correctness

   validates :username, presence: true, uniqueness: true uses presence: true and uniqueness: true correctly together.

3. Final Answer:

   validates :username, presence: true, uniqueness: true -> Option A

4. Quick Check:

   Use single validates with presence and uniqueness [OK]

Hint: Combine presence and uniqueness in one validates call [OK]

Common Mistakes:

• Using deprecated validates_uniqueness_of separately
• Wrong option name 'unique' instead of 'uniqueness'
• Splitting validations unnecessarily