Why Query Builder offers flexibility in Laravel - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a query using Laravel's Query Builder.

Laravel

$users = DB::[1]('users')->get();

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

Aselect

Btable

Cfrom

Dquery

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'select' instead of 'table' to start the query.

The table method starts a query on the specified table, giving flexibility to build queries.

2fill in blank

medium

Complete the code to add a condition to the query.

Laravel

$users = DB::table('users')->where('[1]', 'active')->get();

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

Aid

Bname

Cemail

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'name' or 'email' which are not status indicators.

The where method filters results. Here, filtering users with status equal to 'active' shows flexibility in conditions.

3fill in blank

hard

Fix the error in the code to chain multiple conditions.

Laravel

$users = DB::table('users')->where('status', 'active')->[1]('age', '>', 18)->get();

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

AorWhere

BwhereBetween

Cwhere

Dhaving

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'orWhere' changes the logic to OR instead of AND.

To add multiple conditions that all must be true, chain where methods. This shows flexibility in building complex queries.

4fill in blank

hard

Fill both blanks to select specific columns and order results.

Laravel

$users = DB::table('users')->[1](['name', 'email'])->orderBy('[2]', 'desc')->get();

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

Aselect

Bwhere

Ccreated_at

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'where' instead of 'select' for columns.

The select method chooses columns to retrieve, and orderBy sorts results by a column like created_at. This flexibility lets you customize output.

5fill in blank

hard

Fill all three blanks to group results, count users, and filter groups.

Laravel

$results = DB::table('users')->select('[1]', DB::raw('[2] as user_count'))->groupBy('[3]')->having('user_count', '>', 5)->get();

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

Astatus

Bcount(*)

Dage

Attempts:

3 left

💡 Hint

Common Mistakes

Using different columns for select and groupBy.

This query groups users by status, counts users in each group, and filters groups with more than 5 users. Query Builder's flexibility allows such complex queries easily.

Practice

1. Why does Laravel's Query Builder offer more flexibility compared to writing raw SQL queries?

easy

A. Because it allows building queries step-by-step and modifying them easily

B. Because it only supports simple SELECT statements

C. Because it requires writing raw SQL for every query

D. Because it does not protect against SQL injection

Solution

1. Step 1: Understand Query Builder's design

   Query Builder lets you build queries piece by piece, adding conditions or joins as needed.

2. Step 2: Compare with raw SQL

   Raw SQL requires writing the full query at once and is harder to modify dynamically.

3. Final Answer:

   Because it allows building queries step-by-step and modifying them easily -> Option A

4. Quick Check:

   Step-by-step building = Flexibility [OK]

Hint: Think: step-by-step building means easy changes [OK]

Common Mistakes:

• Assuming Query Builder only supports simple queries
• Thinking raw SQL is easier to modify dynamically
• Believing Query Builder requires raw SQL for all queries

2. Which of the following is the correct syntax to start a Query Builder query in Laravel?

easy

A. $users = DB->table('users')->get();

B. $users = DB::table('users')->get();

C. $users = DB::table['users']->get();

D. $users = DB.table('users').get();

Solution

1. Step 1: Identify correct method call syntax

   Laravel uses double colon :: for static method calls like DB::table('users').

2. Step 2: Check method chaining

   Method chaining uses -> to call get() after table().

3. Final Answer:

   $users = DB::table('users')->get(); -> Option B

4. Quick Check:

   Static call with :: and chaining with -> [OK]

Hint: Remember: DB::table() then ->get() for queries [OK]

Common Mistakes:

• Using -> instead of :: for static calls
• Using square brackets [] instead of parentheses ()
• Using dot notation like DB.table

3. What will be the output of this Laravel Query Builder code?

$query = DB::table('users')->where('age', '>', 18);
$query->where('active', 1);
$results = $query->get();

Choose the correct statement about the query executed.

medium

A. It selects all users without any condition

B. It selects users older than 18 only, ignoring active status

C. It causes a syntax error because of multiple where calls

D. It selects users older than 18 and active users

Solution

1. Step 1: Analyze chained where conditions

   Each where() adds a condition; multiple where calls combine with AND.

2. Step 2: Understand final query effect

   The query filters users with age > 18 AND active = 1.

3. Final Answer:

   It selects users older than 18 and active users -> Option D

4. Quick Check:

   Multiple where = combined conditions [OK]

Hint: Multiple where calls add conditions together [OK]

Common Mistakes:

• Thinking second where replaces the first
• Assuming multiple where calls cause errors
• Ignoring that conditions combine with AND

4. Identify the error in this Laravel Query Builder code:

$query = DB::table('products');
$query->where('price', '>', 100);
$results = $query->get();
$query->where('stock', '>', 0);

medium

A. DB::table() must be called after get()

B. Calling get() twice causes a syntax error

C. Adding where after get() does not affect the executed query

D. You cannot chain where() methods in Query Builder

Solution

1. Step 1: Understand when query executes

   Query executes when get() is called, returning results immediately.

2. Step 2: Check effect of where after get()

   Adding where after get() changes the builder but does not affect already executed query.

3. Final Answer:

   Adding where after get() does not affect the executed query -> Option C

4. Quick Check:

   Query runs at get(), later changes don't affect results [OK]

Hint: Query runs at get(); changes after don't affect results [OK]

Common Mistakes:

• Thinking get() just prepares query without running
• Believing where() can't be chained
• Assuming DB::table() after get() is valid

5. You want to build a query that optionally filters users by city only if a city is provided. Which Query Builder approach offers the most flexibility?

hard

A. Start with DB::table('users') and add ->where('city', $city) only if $city is not empty

B. Write raw SQL with city condition always included

C. Use DB::table('users')->where('city', $city) without checking if $city exists

D. Build the query with all conditions hardcoded before execution

Solution

1. Step 1: Understand conditional query building

   Query Builder lets you add conditions only when needed, making queries flexible.

2. Step 2: Compare options

   Adding where condition only if $city exists avoids unnecessary filters and errors.

3. Final Answer:

   Start with DB::table('users') and add ->where('city', $city) only if $city is not empty -> Option A

4. Quick Check:

   Conditional where = flexible queries [OK]

Hint: Add where condition only if filter value exists [OK]

Common Mistakes:

• Including conditions without checking if values exist
• Using raw SQL losing flexibility and safety
• Hardcoding all conditions before execution