在Laravel 中運(yùn)行原始SQL 查詢的方法有三種主要方式。首先，使用DB::select 方法執(zhí)行原始查詢，傳遞SQL 字符串和綁定參數(shù)數(shù)組，以防止SQL 注入並返回結(jié)果對(duì)像數(shù)組；其次，使用DB::statement() 執(zhí)行插入、更新或刪除操作；最後，使用DB::raw() 在Eloquent 查詢中嵌入原始SQL 片段，適用於復(fù)雜查詢或聚合邏輯，但應(yīng)避免過度使用以保持可維護(hù)性。始終使用參數(shù)綁定來確保安全，並僅在必要時(shí)（如復(fù)雜查詢、性能優(yōu)化或遺留數(shù)據(jù)庫）使用原始SQL，以減少對(duì)特定數(shù)據(jù)庫引擎的依賴。

In Laravel, even though Eloquent ORM is the go-to tool for most database interactions, sometimes you just need to run a raw SQL query. Whether it's for performance, complexity, or convenience, Laravel makes it pretty straightforward.

Here's how to do it right.

Using DB::select for Raw Queries

The simplest way to run a raw SQL query is by using the DB::select method. It allows you to write plain SQL while still benefiting from Laravel's database connection handling and result hydration.

 use Illuminate\Support\Facades\DB;

$results = DB::select('SELECT * FROM users WHERE active = ?', [1]);

• The first argument is your SQL string.
• The second is an array of bindings — this helps prevent SQL injection.
• It returns an array of PHP objects, so you can loop through them or access fields directly.

If you're not selecting data but running an insert, update, or delete, use DB::statement() instead.

Binding Parameters the Right Way

When writing raw queries, always use parameter binding instead of concatenating values directly into the SQL string. This avoids SQL injection vulnerabilities.

For example, here's how you should do it:

 $userId = 5;
$results = DB::select('SELECT * FROM orders WHERE user_id = ?', [$userId]);

Or, if you prefer named bindings (especially useful for longer queries):

 $results = DB::select('SELECT * FROM users WHERE id = :id', ['id' => 5]);

• Use ? for positional placeholders
• Or use :name for named placeholders
• Pass the values in an array as the second argument

This keeps your query secure and readable.

Running Raw Queries in Eloquent Models

If you're using Eloquent but still want to write raw SQL, you can use the DB::raw() method inside your queries.

For example:

 $users = User::select(['id', 'name', DB::raw('COUNT(orders.id) as order_count')])
    ->leftJoin('orders', 'orders.user_id', '=', 'users.id')
    ->groupBy('users.id')
    ->get();

• DB::raw() tells Laravel to treat that part as raw SQL
• It's useful when building complex queries with aggregations or custom logic
• You can also use it in where clauses or order by statements

But be careful: if you overuse DB::raw , your query can become hard to maintain or test.

When to Use Raw Queries

You don't need raw SQL for every situation, but there are times when it makes sense:

• When dealing with complex joins or subqueries that are hard to express with query builder methods
• For performance-critical parts of your app where you want full control over the SQL
• When working with legacy databases that don't follow Laravel's naming or structure conventions

Just remember: raw SQL ties you more closely to a specific database engine, so if you plan to switch databases later, it might complicate things.

Basically, that's how you safely and effectively run raw SQL queries in Laravel. It's not complicated, but it does require attention to security and structure.

以上是如何在Laravel執(zhí)行原始SQL查詢？的詳細(xì)內(nèi)容。更多資訊請關(guān)注PHP中文網(wǎng)其他相關(guān)文章！