Uniqueness validation in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of uniqueness validation in Rails?

Uniqueness validation ensures that a specific attribute value is unique in the database, preventing duplicate records for that attribute.

beginner

How do you add a uniqueness validation to a model attribute in Rails?

Use validates :attribute_name, uniqueness: true inside the model to enforce uniqueness on that attribute.

intermediate

Why should you add a unique index in the database when using uniqueness validation?

Because Rails validations run in application code and can miss race conditions, a unique database index ensures data integrity at the database level.

intermediate

What option do you use to make uniqueness validation case insensitive?

Use validates :attribute_name, uniqueness: { case_sensitive: false } to ignore case differences when checking uniqueness.

intermediate

How can you validate uniqueness scoped to another attribute in Rails?

Use validates :attribute_name, uniqueness: { scope: :other_attribute } to ensure uniqueness within the scope of another attribute.

Which Rails method adds uniqueness validation to a model attribute?

A validates :name, uniqueness: true

B validate_uniqueness_of :name

C unique :name

D validates_uniqueness :name

The correct syntax is validates :attribute, uniqueness: true.

Why is it important to add a unique index in the database when using uniqueness validation?

A To improve query speed

B To prevent race conditions causing duplicates

C To allow duplicate records

D To enable case insensitive checks

A unique index prevents duplicates even if two requests happen at the same time, which Rails validations alone cannot guarantee.

How do you make uniqueness validation ignore case differences?

A validates :attr, uniqueness: true, ignore_case: true

B validates :attr, case_insensitive: true

C validates :attr, uniqueness: { case_sensitive: false }

D validates :attr, uniqueness: false

Use case_sensitive: false option inside uniqueness validation to ignore case.

What does the scope option do in uniqueness validation?

A Makes validation faster

B Disables uniqueness validation

C Allows duplicates globally

D Limits uniqueness to a group of records sharing the same scope attribute

The scope option restricts uniqueness to records with the same value in the scoped attribute.

If you want to validate uniqueness of email ignoring case and scoped to account_id, which is correct?

A validates :email, uniqueness: { case_sensitive: false, scope: :account_id }

B validates :email, uniqueness: true, scope: :account_id

C validates :email, uniqueness: { scope: :account_id }

D validates :email, uniqueness: false

You combine case_sensitive: false and scope: :account_id inside uniqueness validation.

Explain how to enforce uniqueness validation on a Rails model attribute and why adding a unique database index is important.

Think about both application-level and database-level protections.

Describe how to make uniqueness validation case insensitive and scoped to another attribute in Rails.

Combine options inside the uniqueness hash.

Practice

1. What does validates :email, uniqueness: true do in a Rails model?

easy

A. Deletes duplicate email records from the database

B. Prevents saving records with duplicate email values

C. Allows multiple records with the same email

D. Automatically encrypts the email field

Solution

1. Step 1: Understand uniqueness validation purpose

   Uniqueness validation ensures no two records have the same value for the specified field.

2. Step 2: Apply to the email field

   Using validates :email, uniqueness: true means Rails will check that the email is unique before saving.

3. Final Answer:

   Prevents saving records with duplicate email values -> Option B

4. Quick Check:

   Uniqueness validation = prevents duplicates [OK]

Hint: Uniqueness validation stops duplicate field values [OK]

Common Mistakes:

• Thinking it encrypts data
• Assuming it deletes duplicates automatically
• Believing it allows duplicates

2. Which is the correct syntax to add uniqueness validation for a username in a Rails model?

easy

A. validates :username, unique: true

B. validate :username, uniqueness: true

C. validates :username, uniqueness: true

D. validates_uniqueness_of :username, true

Solution

1. Step 1: Recall Rails validation syntax

   Rails uses validates :field, uniqueness: true for uniqueness validation.

2. Step 2: Check each option

   validates :username, uniqueness: true matches the correct syntax exactly; others have syntax errors or deprecated style.

3. Final Answer:

   validates :username, uniqueness: true -> Option C

4. Quick Check:

   Correct uniqueness syntax = validates :field, uniqueness: true [OK]

Hint: Use 'validates :field, uniqueness: true' syntax [OK]

Common Mistakes:

• Using 'unique' instead of 'uniqueness'
• Using 'validate' instead of 'validates'
• Using deprecated 'validates_uniqueness_of' syntax incorrectly

3. Given this model code:

class User < ApplicationRecord
  validates :email, uniqueness: true
end

What happens if you try to save two users with the same email?

medium

A. The second user fails to save due to validation error

B. Both users save successfully

C. An exception is raised immediately

D. The database automatically rejects the second user

Solution

1. Step 1: Understand Rails validation behavior

   Uniqueness validation runs before saving and prevents duplicates by adding errors.

2. Step 2: Effect on saving duplicate email

   The first user saves fine; the second user triggers validation failure and does not save.

3. Final Answer:

   The second user fails to save due to validation error -> Option A

4. Quick Check:

   Uniqueness validation blocks duplicates on save [OK]

Hint: Second duplicate save triggers validation error [OK]

Common Mistakes:

• Thinking both save successfully
• Expecting a database exception instead of validation error
• Assuming database rejects without validation

4. Identify the problem in this model code:

class Product < ApplicationRecord
  validates :code, uniqueness: true
  validates :code, presence: true
end

Why might duplicates still be saved?

medium

A. Uniqueness validation is case sensitive by default

B. Presence validation conflicts with uniqueness validation

C. The validations are in the wrong order

D. No unique index exists in the database for code

Solution

1. Step 1: Understand validation vs database constraints

   Rails validations check before saving but do not guarantee uniqueness at the database level.

2. Step 2: Check for unique index necessity

   Without a unique database index on code, race conditions can allow duplicates.

3. Final Answer:

   No unique index exists in the database for code -> Option D

4. Quick Check:

   Validation alone can't prevent duplicates without DB index [OK]

Hint: Add unique DB index to fully prevent duplicates [OK]

Common Mistakes:

• Assuming validations alone guarantee uniqueness
• Confusing presence and uniqueness validations
• Thinking validation order matters here

5. You want to ensure usernames are unique but case insensitive (e.g., 'User1' and 'user1' count as duplicates). How do you write the validation?

hard

A. validates :username, uniqueness: { case_sensitive: false }

B. validates :username, uniqueness: true, case_sensitive: false

C. validates :username, unique: { case_sensitive: false }

D. validates_uniqueness_of :username, case_sensitive: true

Solution

1. Step 1: Recall uniqueness validation options

   To make uniqueness case insensitive, use uniqueness: { case_sensitive: false }.

2. Step 2: Check each option's correctness

   validates :username, uniqueness: { case_sensitive: false } uses correct syntax and option key; others have syntax errors or wrong case sensitivity.

3. Final Answer:

   validates :username, uniqueness: { case_sensitive: false } -> Option A

4. Quick Check:

   Case insensitive uniqueness = uniqueness: { case_sensitive: false } [OK]

Hint: Use uniqueness with case_sensitive: false for case insensitivity [OK]

Common Mistakes:

• Placing case_sensitive outside uniqueness hash
• Using 'unique' instead of 'uniqueness'
• Setting case_sensitive to true by mistake