Why query interface abstracts SQL in Ruby on Rails - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to fetch all users from the database using ActiveRecord.

Ruby on Rails

users = User.[1]

Drag options to blanks, or click blank then click option'

Aall

Bselect

Cget

Dfetch

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'fetch' or 'get' which are not ActiveRecord methods for fetching all records.

The all method fetches all records from the users table using ActiveRecord's query interface.

2fill in blank

medium

Complete the code to find users with age greater than 30 using ActiveRecord query interface.

Ruby on Rails

users = User.where("age [1] ?", 30)

Drag options to blanks, or click blank then click option'

A>

B<

C=

D<=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' or '=' which would select wrong users.

The where method uses SQL conditions. To find users older than 30, use the '>' operator.

3fill in blank

hard

Fix the error in the code to order users by name ascending.

Ruby on Rails

users = User.order(name: [1])

Drag options to blanks, or click blank then click option'

A:desc

Bname

C:asc

Dorder

Attempts:

3 left

💡 Hint

Common Mistakes

Using ':desc' which orders descending.

Passing a string instead of a symbol.

The order method accepts :asc or :desc symbols to specify ascending or descending order. Use :asc for ascending.

4fill in blank

hard

Fill both blanks to select users with name starting with 'A' and order by age descending.

Ruby on Rails

users = User.where("name [1] ?", 'A%').order('age [2]')

Drag options to blanks, or click blank then click option'

ALIKE

BASC

CDESC

D=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' instead of 'LIKE' for pattern matching.

Ordering ascending instead of descending.

Use LIKE to match names starting with 'A'. Use DESC to order age descending.

5fill in blank

hard

Fill all three blanks to create a hash mapping user emails to their names for users older than 25.

Ruby on Rails

result = User.where("age [1] ?", 25).pluck([2], [3]).to_h

Drag options to blanks, or click blank then click option'

A>

B:email

C:name

D:age

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' or '=' for age filter.

Plucking wrong columns like age instead of email or name.

Use '>' to filter users older than 25. pluck extracts email and name columns. to_h converts array pairs to a hash.

Practice

1. Why does Rails use a query interface to abstract SQL instead of writing raw SQL directly?

easy

A. To prevent any database access at all

B. To make the application run faster by skipping the database

C. To force developers to learn SQL syntax

D. To make database queries safer and easier to write

Solution

1. Step 1: Understand the purpose of abstraction

   The query interface hides the complexity of SQL behind simple Ruby methods.

2. Step 2: Recognize benefits of abstraction

   This makes queries safer by preventing SQL injection and easier to write and maintain.

3. Final Answer:

   To make database queries safer and easier to write -> Option D

4. Quick Check:

   Query interface improves safety and simplicity = A [OK]

Hint: Think: abstraction means simpler, safer code [OK]

Common Mistakes:

• Thinking abstraction makes code slower
• Believing it forces SQL learning
• Assuming it blocks database access

2. Which of the following is the correct Rails query interface syntax to find all users with age greater than 30?

easy

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

B. User.find('age > 30')

C. User.select(age > 30)

D. User.get(age > 30)

Solution

1. Step 1: Identify correct method for filtering

   Rails uses where to filter records with conditions.

2. Step 2: Check syntax for conditions

   Using where('age > ?', 30) safely inserts the value and avoids SQL injection.

3. Final Answer:

   User.where('age > ?', 30) -> Option A

4. Quick Check:

   Correct method and safe syntax = D [OK]

Hint: Remember: use where with placeholders for conditions [OK]

Common Mistakes:

• Using find instead of where for conditions
• Passing raw conditions without placeholders
• Using non-existent methods like get or select for filtering

3. Given the Rails query: User.where(active: true).order(created_at: :desc).limit(3), what does this return?

medium

A. The last 3 active users created, newest first

B. All active users sorted by creation date ascending

C. The first 3 users created, regardless of active status

D. An error because chaining is not allowed

Solution

1. Step 1: Analyze the where clause

   where(active: true) filters users who are active.

2. Step 2: Understand order and limit

   order(created_at: :desc) sorts newest first, and limit(3) restricts to 3 records.

3. Final Answer:

   The last 3 active users created, newest first -> Option A

4. Quick Check:

   Filter active + newest 3 = C [OK]

Hint: Chain filters, order, and limit to get precise results [OK]

Common Mistakes:

• Ignoring the order direction
• Confusing limit with offset
• Thinking chaining causes errors

4. What is wrong with this Rails query? User.where('age > 20').order(:name).limit('five')

medium

A. The where clause syntax is incorrect

B. The limit argument should be a number, not a string

C. Order cannot be used after where

D. There is no User model in Rails

Solution

1. Step 1: Check the limit argument type

   limit expects an integer, but 'five' is a string, causing an error.

2. Step 2: Verify other parts

   where('age > 20') and order(:name) are valid syntax and chaining is allowed.

3. Final Answer:

   The limit argument should be a number, not a string -> Option B

4. Quick Check:

   limit needs integer, not string = A [OK]

Hint: limit must be a number, not text [OK]

Common Mistakes:

• Thinking where syntax is wrong without placeholders
• Believing order can't follow where
• Assuming User model doesn't exist

5. You want to get all users who are either active or have signed up in the last 7 days. Which Rails query interface code correctly abstracts this SQL logic?

hard

A. User.where('active = true OR created_at >= 7.days.ago')

B. User.find_by(active: true, created_at: 7.days.ago..Time.now)

C. User.where(active: true).or(User.where('created_at >= ?', 7.days.ago))

D. User.where(active: true && created_at >= 7.days.ago)

Solution

1. Step 1: Understand the OR condition in Rails

   Rails query interface uses or to combine two where queries with OR logic.

2. Step 2: Check each option's correctness

   User.where(active: true).or(User.where('created_at >= ?', 7.days.ago)) correctly uses or with safe placeholders. User.where('active = true OR created_at >= 7.days.ago') is invalid because it treats Ruby code as a string. User.find_by(active: true, created_at: 7.days.ago..Time.now) uses find_by which returns one record, not all. User.where(active: true && created_at >= 7.days.ago) uses invalid Ruby syntax inside where.

3. Final Answer:

   User.where(active: true).or(User.where('created_at >= ?', 7.days.ago)) -> Option C

4. Quick Check:

   Use or to combine where queries = B [OK]

Hint: Use .or to combine two where queries safely [OK]

Common Mistakes:

• Putting Ruby code inside SQL strings
• Using find_by instead of where for multiple records
• Using && inside where instead of chaining or or