PHP Laravel闭包理解：whereExists中$query参数来源疑问

Great question—this is one of those clean, "magic" parts of Laravel's query builder that makes writing complex queries easy, but it’s totally normal to wonder where that $query comes from! Let’s break it down clearly.

Where does the $query parameter come from? #

That $query is a fresh instance of Laravel's Query Builder (specifically Illuminate\Database\Query\Builder for raw table queries, or Illuminate\Database\Eloquent\Builder if you’re using Eloquent models). You never have to create it yourself—Laravel handles instantiating and passing it to your closure automatically.

The Underlying Passing Logic #

When you call whereExists() on a query builder instance (like DB::table('users')), here’s what happens behind the scenes:

1. The whereExists method accepts your closure as its argument.
2. Laravel creates a brand new, empty Query Builder object designed specifically for your subquery.
3. It passes this new Query Builder instance directly into your closure as the $query parameter.
4. You use that $query to define your subquery logic (in your example, selecting from the orders table and linking it to the main users table).
5. Finally, Laravel compiles the subquery you built into SQL and wraps it into the EXISTS(...) clause of your main users query.

Why this pattern works so well #

This is a consistent pattern across Laravel’s query tools—you’ll see the same behavior with methods like whereHas, with, or whereInSub. Laravel takes care of the boilerplate of creating query builder instances so you can focus on writing the actual logic of your query, not instantiating objects.

To tie this directly to your code:

DB::table('users')->whereExists(function ($query) {
    // $query is a Laravel Query Builder instance created & passed by Laravel
    $query->select(DB::raw(1))
          ->from('orders')
          ->whereRaw('orders.user_id = users.id');
})->get();

Laravel handles all the heavy lifting of creating that $query instance and passing it into your closure, then translates your closure’s logic into valid SQL.

内容的提问来源于stack exchange，提问作者Grennard