Raw expressions in Laravel - Performance & Optimization

Performance: Raw expressions

MEDIUM IMPACT

Using raw expressions affects how queries are built and executed, impacting database query performance and server response time.

Including complex SQL conditions in a Laravel query

Laravel

$year = 2023;
$users = DB::table('users')->whereYear('created_at', $year)->get();

Using Laravel's built-in methods allows query builder to optimize and safely bind parameters.

📈 Performance GainEnables query caching and safer execution, reducing server load

Including complex SQL conditions in a Laravel query

Laravel

$users = DB::table('users')->whereRaw('YEAR(created_at) = 2023')->get();

Using raw SQL without bindings can lead to SQL injection risks and may prevent query caching.

📉 Performance CostBlocks query optimization and can increase server processing time

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Raw SQL with whereRaw	N/A	N/A	N/A	[!] Caution
Laravel query builder methods	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Raw expressions affect the backend query generation stage before data reaches the frontend, influencing how fast data is retrieved and sent to the browser.

→Server Query Execution

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Query Execution

Core Web Vital Affected

LCP

Using raw expressions affects how queries are built and executed, impacting database query performance and server response time.

Optimization Tips

1Avoid raw expressions without parameter binding to prevent SQL injection and improve query caching.

2Prefer Laravel query builder methods for safer and more optimized queries.

3Monitor backend query times to ensure fast data delivery and better LCP.

Performance Quiz - 3 Questions

What is a main performance risk when using raw expressions in Laravel queries?

A SQL injection and lack of query optimization

B Increased DOM reflows in the browser

C Slower CSS rendering

D Higher JavaScript bundle size

DevTools: Network

How to check: Open DevTools, go to Network tab, filter XHR requests, and inspect the response time of API calls that use raw expressions.

What to look for: Look for slow response times indicating inefficient queries or large payloads affecting LCP.

Practice

1. What is the primary purpose of using DB::raw() in Laravel queries?

easy

A. To insert raw SQL expressions directly into the query builder

B. To automatically escape all user inputs

C. To convert Eloquent models into arrays

D. To cache query results for faster access

Solution

1. Step 1: Understand the role of DB::raw()

   DB::raw() allows you to write raw SQL expressions inside Laravel's query builder without modification.

2. Step 2: Compare with other options

   Options B, C, and D describe different Laravel features unrelated to raw SQL expressions.

3. Final Answer:

   To insert raw SQL expressions directly into the query builder -> Option A

4. Quick Check:

   DB::raw() = raw SQL insertion [OK]

Hint: DB::raw() means write SQL exactly as is inside queries [OK]

Common Mistakes:

• Thinking DB::raw() escapes inputs automatically
• Confusing DB::raw() with model conversion
• Assuming DB::raw() caches queries

2. Which of the following is the correct syntax to use DB::raw() in a Laravel query builder to select the current date?

easy

A. DB::table('users')->select(DB::raw('CURRENT_DATE'))->get();

B. DB::table('users')->select('CURRENT_DATE')->get();

C. DB::table('users')->selectRaw('CURRENT_DATE')->get();

D. DB::table('users')->selectRaw(DB::raw('CURRENT_DATE'))->get();

Solution

1. Step 1: Identify correct raw expression usage

   DB::raw() wraps the raw SQL string inside select() to insert it as is.

2. Step 2: Analyze other options

   DB::table('users')->select('CURRENT_DATE')->get(); treats 'CURRENT_DATE' as a column name, not raw SQL. DB::table('users')->selectRaw('CURRENT_DATE')->get(); uses selectRaw() correctly but without DB::raw(), which is valid but not the exact syntax asked. DB::table('users')->selectRaw(DB::raw('CURRENT_DATE'))->get(); nests DB::raw() inside selectRaw(), which is incorrect.

3. Final Answer:

   DB::table('users')->select(DB::raw('CURRENT_DATE'))->get(); -> Option A

4. Quick Check:

   Use DB::raw() inside select() for raw SQL [OK]

Hint: Use DB::raw('SQL') inside select() for raw SQL [OK]

Common Mistakes:

• Using select() with string instead of DB::raw()
• Confusing selectRaw() and DB::raw() usage
• Nesting DB::raw() inside selectRaw() incorrectly

3. What will be the output of the following Laravel query?

DB::table('orders')
  ->select('id', DB::raw('price * quantity AS total'))
  ->where('status', 'completed')
  ->get();

medium

A. An empty collection because raw expressions are not supported in where clauses

B. A syntax error because raw expressions cannot have aliases

C. A collection of orders with id and a calculated total price (price * quantity)

D. A collection with only id and price fields, ignoring quantity

Solution

1. Step 1: Understand the select with DB::raw()

   The query selects 'id' and a raw SQL expression calculating 'price * quantity' as 'total'. This is valid and returns those fields.

2. Step 2: Check the where clause and output

   The where clause filters orders with status 'completed'. The output is a collection of matching orders with 'id' and 'total' fields.

3. Final Answer:

   A collection of orders with id and a calculated total price (price * quantity) -> Option C

4. Quick Check:

   DB::raw() with alias returns calculated fields [OK]

Hint: DB::raw() can calculate fields with aliases in select [OK]

Common Mistakes:

• Thinking raw expressions cannot have aliases
• Assuming raw expressions affect where clause support
• Ignoring the calculated field in output

4. Identify the error in this Laravel query using raw expressions:

DB::table('users')
  ->where(DB::raw('LENGTH(name)'), '>', 5)
  ->get();

medium

A. Raw expressions cannot be used inside where clauses

B. The syntax is correct; no error present

C. DB::raw() should be wrapped inside a closure for where

D. The comparison operator '>' is invalid in this context

Solution

1. Step 1: Review usage of DB::raw() in where clause

   Using DB::raw() inside where to apply SQL functions like LENGTH() is valid syntax in Laravel.

2. Step 2: Check operators and syntax

   The '>' operator is valid for comparison. No wrapping closure is required here.

3. Final Answer:

   The syntax is correct; no error present -> Option B

4. Quick Check:

   DB::raw() works in where clauses with operators [OK]

Hint: DB::raw() can be used directly in where with operators [OK]

Common Mistakes:

• Assuming raw expressions are disallowed in where
• Thinking a closure is needed for DB::raw() in where
• Misunderstanding comparison operator validity

5. You want to update all users' scores by adding 10 points using a raw SQL expression in Laravel. Which code snippet correctly achieves this safely?

hard

A. DB::table('users')->update(DB::raw('score = score + 10'));

B. DB::table('users')->update(['score' => 'score + 10']);

C. DB::table('users')->updateRaw('score = score + 10');

D. DB::table('users')->update(['score' => DB::raw('score + 10')]);

Solution

1. Step 1: Understand how to update with raw expressions

   To update a column by adding a value, use DB::raw() inside the update array to write the SQL expression.

2. Step 2: Analyze each option

   DB::table('users')->update(['score' => DB::raw('score + 10')]); correctly uses DB::raw('score + 10') as the new value. DB::table('users')->update(['score' => 'score + 10']); treats it as a string, not SQL. DB::table('users')->update(DB::raw('score = score + 10')); passes DB::raw() directly to update(), which expects an array, causing error. DB::table('users')->updateRaw('score = score + 10'); uses a non-existent updateRaw() method.

3. Final Answer:

   DB::table('users')->update(['score' => DB::raw('score + 10')]); -> Option D

4. Quick Check:

   Use DB::raw() inside update array for calculations [OK]

Hint: Use DB::raw() inside update array for arithmetic updates [OK]

Common Mistakes:

• Passing raw SQL as string without DB::raw()
• Calling non-existent updateRaw() method
• Passing DB::raw() directly instead of in array