Where conditions in Ruby on Rails - Performance & Optimization

Performance: Where conditions

MEDIUM IMPACT

This affects how quickly the database query returns results and how much data the server processes before sending to the browser.

Filtering database records with conditions

Ruby on Rails

User.where(active: true).where('age > ?', 30)

Filters records at the database level, returning only needed data quickly.

📈 Performance GainReduces data transferred; faster query execution; improves LCP

Filtering database records with conditions

Ruby on Rails

User.all.select { |user| user.active? && user.age > 30 }

Loads all users into memory then filters, causing slow response and high memory use.

📉 Performance CostBlocks rendering while loading all records; high memory usage; slow query response

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Filtering in Ruby after loading all records	N/A	N/A	Blocks rendering due to slow data	[X] Bad
Filtering with ActiveRecord where conditions	N/A	N/A	Faster rendering due to less data	[OK] Good

Rendering Pipeline

Where conditions affect the server's data fetching step before rendering HTML. Efficient queries reduce server processing and data sent to the browser, speeding up the critical rendering path.

→Data Fetching

→Server Processing

→HTML Rendering

⚠️ BottleneckData Fetching from database

Core Web Vital Affected

LCP

This affects how quickly the database query returns results and how much data the server processes before sending to the browser.

Optimization Tips

1Always filter data at the database level using where conditions.

2Avoid loading all records into memory before filtering.

3Chain where calls to build precise queries and reduce data size.

Performance Quiz - 3 Questions

Why is filtering records with where conditions in the database better than filtering in Ruby after loading all records?

A Because Ruby filtering is faster than database filtering

B Because it reduces data transferred and speeds up server response

C Because it increases memory usage on the server

D Because it delays rendering until all data is loaded

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and inspect the API or page request timing and response size.

What to look for: Look for smaller response sizes and faster server response times indicating efficient queries.

Practice

1. What does the where method do in Rails ActiveRecord?

easy

A. Creates a new database table

B. Deletes records from the database

C. Updates all records without conditions

D. Filters records based on given conditions

Solution

1. Step 1: Understand the purpose of where

   The where method is used to specify conditions to filter records in a database query.

2. Step 2: Compare with other database actions

   Deleting, creating tables, or updating all records are different methods like delete, migrations, or update_all.

3. Final Answer:

   Filters records based on given conditions -> Option D

4. Quick Check:

   where filters records = C [OK]

Hint: Remember: where narrows down records by conditions [OK]

Common Mistakes:

• Confusing where with delete or update methods
• Thinking where creates or deletes tables
• Assuming where modifies all records without conditions

2. Which of the following is the correct syntax to find users with age 30 using where?

easy

A. User.where('age == ?', 30)

B. User.where(age: 30)

C. User.where(age == 30)

D. User.where(age = 30)

Solution

1. Step 1: Identify correct hash syntax for where

   Using a hash like age: 30 is the standard way to filter by attribute value.

2. Step 2: Check other options for syntax errors

   User.where('age == ?', 30) uses invalid SQL operator ==; User.where(age == 30) uses invalid Ruby comparison inside where; User.where(age = 30) uses assignment instead of comparison.

3. Final Answer:

   User.where(age: 30) -> Option B

4. Quick Check:

   Hash syntax for where = A [OK]

Hint: Use hash syntax for simple where conditions [OK]

Common Mistakes:

• Using == inside where instead of hash or string
• Using = instead of : or ? for conditions
• Confusing string and hash syntax

3. What will this code return?

User.where("name LIKE ?", "%John%")

medium

A. All users with name containing 'John'

B. All users with name exactly 'John'

C. Syntax error due to quotes

D. No users because LIKE is invalid

Solution

1. Step 1: Understand the SQL LIKE operator

   LIKE with % means match any characters before or after 'John', so it finds names containing 'John'.

2. Step 2: Check the where syntax

   The string with placeholder and argument is correct syntax for complex conditions.

3. Final Answer:

   All users with name containing 'John' -> Option A

4. Quick Check:

   LIKE with % means contains = A [OK]

Hint: LIKE with % means contains substring [OK]

Common Mistakes:

• Thinking LIKE matches exact string only
• Confusing syntax with invalid quotes
• Assuming LIKE is not supported in where

4. Identify the error in this code:

User.where(age > 25)

medium

A. Incorrect use of > inside where without string

B. Should use User.find instead of where

C. No error, code works fine

D. Missing quotes around condition string

Solution

1. Step 1: Check syntax of where conditions

   Conditions with operators like > must be inside a string or hash syntax; direct Ruby expressions are invalid.

2. Step 2: Identify correct usage

   Correct usage is User.where("age > ?", 25) or User.where("age > 25").

3. Final Answer:

   Incorrect use of > inside where without string -> Option A

4. Quick Check:

   Operators need string syntax in where = D [OK]

Hint: Use strings for operators like > in where [OK]

Common Mistakes:

• Writing Ruby expressions directly inside where
• Forgetting to quote conditions with operators
• Using find instead of where for filtering

5. How can you chain multiple where conditions to find users who are active and older than 18?

hard

A. User.where(active: true, age > ?, 18)

B. User.where('active = true AND age > ?')

C. User.where(active: true).where('age > ?', 18)

D. User.where(active == true).where(age > 18)

Solution

1. Step 1: Understand chaining of where

   Multiple where calls can be chained to combine conditions, each filtering further.

2. Step 2: Check syntax of each where call

   First where uses hash for simple boolean, second uses string with placeholder for age condition.

3. Step 3: Evaluate other options

   User.where(active: true, age > ?, 18) uses invalid Ruby expression without quotes; User.where('active = true AND age > ?') uses placeholder without bind argument; User.where(active == true).where(age > 18) uses invalid Ruby expressions.

4. Final Answer:

   User.where(active: true).where('age > ?', 18) -> Option C

5. Quick Check:

   Chain where with hash and string = B [OK]

Hint: Chain where calls for multiple conditions [OK]

Common Mistakes:

• Mixing hash and string in one where call incorrectly
• Using == inside where instead of : or placeholders
• Not chaining where calls properly