Why Query Builder offers flexibility in Laravel - See It in Action

Why Query Builder offers flexibility

📖 Scenario: You are building a small Laravel application to manage a bookstore's inventory. You want to fetch books based on different conditions like price, author, and availability. Using Laravel's Query Builder will help you write flexible and readable database queries.

🎯 Goal: Build a Laravel Query Builder example that shows how to flexibly fetch books from the database using different conditions and chaining methods.

📋 What You'll Learn

Create a $books variable with a base query selecting from the books table

Add a configuration variable $maxPrice to filter books cheaper than this price

Use Query Builder methods to filter books where price is less than $maxPrice and available is true

Complete the query by ordering the results by title ascending

💡 Why This Matters

🌍 Real World

Query Builder helps developers write database queries that are easy to read, modify, and maintain without writing raw SQL. This flexibility is useful in real applications where query conditions change based on user input or business rules.

💼 Career

Understanding Query Builder is essential for Laravel developers to build efficient and secure database interactions. It improves productivity and reduces errors compared to raw SQL queries.

1

DATA SETUP: Create base query for books

Create a variable called $books and set it to a Query Builder instance selecting from the books table using DB::table('books').

Laravel

<?php

use Illuminate\Support\Facades\DB;

// Create a variable $books with DB::table('books')
// Your code here

Hint

Use DB::table('books') to start the query.

2

CONFIGURATION: Define maximum price filter

Add a variable called $maxPrice and set it to 20 to use as a price filter.

Laravel

<?php

use Illuminate\Support\Facades\DB;

$books = DB::table('books');

// Define $maxPrice as 20
// Your code here

Hint

Just create a variable $maxPrice and assign it the number 20.

3

CORE LOGIC: Add filters using Query Builder methods

Use the where method on $books to filter where price is less than $maxPrice and where available is true. Chain these methods to $books.

Laravel

<?php

use Illuminate\Support\Facades\DB;

$books = DB::table('books');

$maxPrice = 20;

// Add where conditions for price < $maxPrice and available = true
// Your code here

Hint

Chain two where calls on $books to filter by price and availability.

4

COMPLETION: Order results by title ascending

Complete the query by chaining the orderBy method on $books to sort results by title in ascending order.

Laravel

where('price', 'where('available', true);

// Add orderBy to sort by title ascending
// Your code here

Hint

Use orderBy('title', 'asc') chained to $books.

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