Laravel's Query Builder provides a smooth way to build database queries without writing native SQL. 1. Use the DB facade to directly query table data, such as DB::table('users')->get() to get all users; 2. Common methods include get(), first(), pluck(), take() for data retrieval, where(), orWhere(), whereIn(), whereNull() add conditions, orderBy(), latest() sort, join() association table, count(), max() and other aggregate functions; 3. Support insert() insert() to insert data, update() update() to update data, delete() delete data, and truncate() clear table; 4. Advanced usage includes DB::raw() to execute native expressions, when() conditional query, and subquery nesting; 5. It can be used in combination with the Eloquent model, such as User::where()->get() to return model instances; Query Builder is suitable for complex queries and has better performance than Eloquent. During debugging, you can view SQL statements toSql() to ultimately achieve concise and efficient database operations.
Laravel's Query Builder is a powerful and fluent way to construct and run database queries without writing raw SQL. It's part of Laravel's Eloquent ORM but can be used independently with database tables. Here's how to use it effectively.

1. Using the DB Facade
To start using the Query Builder, import and use Laravel's DB
facade:
use Illuminate\Support\Facades\DB;
Then you can query any table like this:

$users = DB::table('users')->get();
This retrieves all rows from the users
table.
2. Common Query Builder Methods
Here are the most commonly used methods with examples:

? Retrieve Data
Get all rows:
$users = DB::table('users')->get();
Get first row:
$user = DB::table('users')->first();
Get specific columns:
$names = DB::table('users')->pluck('name');
Limit results:
$someUsers = DB::table('users')->take(5)->get();
? Add WHERE Clauses
Simple where:
$user = DB::table('users')->where('active', 1)->get();
Chained conditions (AND):
$user = DB::table('users') ->where('status', 'active') ->where('age', '>', 18) ->get();
OR conditions:
$user = DB::table('users') ->where('votes', '>', 100) ->orWhere('name', 'John') ->get();
Where in:
$users = DB::table('users') ->whereIn('id', [1, 2, 3]) ->get();
Null checks:
$users = DB::table('users') ->whereNull('updated_at') ->get();
? Sorting & Ordering
$users = DB::table('users') ->orderBy('name', 'desc') ->get();
You can also use latest()
and oldest()
for timestamp columns:
$user = DB::table('users')->latest()->first();
? Joins
$users = DB::table('users') ->join('contacts', 'users.id', '=', 'contacts.user_id') ->select('users.name', 'contacts.phone') ->get();
Supports
leftJoin
,rightJoin
, etc.
? Aggregates
$count = DB::table('users')->count(); $max = DB::table('orders')->max('price'); $avg = DB::table('orders')->avg('price');
3. Insert, Update, Delete
? Insert Data
DB::table('users')->insert([ 'name' => 'John Doe', 'email' => 'john@example.com', 'created_at' => now(), 'updated_at' => now(), ]);
For getting the inserted ID (if the table has an auto-incrementing ID):
$id = DB::table('users')->insertGetId([ 'name' => 'Jane Doe', 'email' => 'jane@example.com', 'created_at' => now(), 'updated_at' => now(), ]);
? Update Data
$affected = DB::table('users') ->where('id', 1) ->update([ 'email' => 'newemail@example.com', 'updated_at' => now(), ]);
Returns the number of affected rows.
? Delete Data
$deleted = DB::table('users') ->where('id', 1) ->delete();
Or delete all:
DB::table('users')->truncate(); // Removes all rows
4. Advanced Usage
? Raw Expressions
Use DB::raw()
to inject raw SQL:
$users = DB::table('users') ->select(DB::raw('count(*) as user_count, status')) ->where('status', '<>', 1) ->groupBy('status') ->get();
Be cautious with raw expressions to avoid SQL injection.
? Conditional Clauses
Use when()
to apply conditions only when needed:
$role = 'admin'; $users = DB::table('users') ->when($role, function ($query, $role) { return $query->where('role', $role); }) ->get();
This only applies the where
clause if $role
is truthy.
? Subqueries (Laravel 6)
$latestLogin = DB::table('logins') ->select('user_id') ->whereColumn('user_id', 'users.id') ->orderBy('login_at', 'desc') ->limit(1); $users = DB::table('users') ->select('users.*') ->where('id', 'in', $latestLogin) ->get();
5. Using with Models (Eloquent)
Even though Eloquent models use the Query Builder under the hood, you can still use it directly on models:
$users = User::where('active', 1)->orderBy('name')->get();
This returns Eloquent models, not plain objects.
Final Notes
- The Query Builder is great for complex queries or when you don't need full Eloquent features.
- It's faster than Eloquent for simple operations because it doesn't instantiate model objects.
- Always sanitize input when using raw expressions.
- Use
dd()
ortoSql()
dd()
for debugging:
$query = DB::table('users')->where('active', 1); echo $query->toSql(); // SELECT * FROM users WHERE active = ?
Basically, the Query Builder gives you a clean, expressive way to interact with your database — no raw SQL needed in most cases.
The above is the detailed content of How to use the query builder in Laravel?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

There are three ways to add custom validation rules in Laravel: using closures, Rule classes, and form requests. 1. Use closures to be suitable for lightweight verification, such as preventing the user name "admin"; 2. Create Rule classes (such as ValidUsernameRule) to make complex logic clearer and maintainable; 3. Integrate multiple rules in form requests and centrally manage verification logic. At the same time, you can set prompts through custom messages methods or incoming error message arrays to improve flexibility and maintainability.

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

Dependency injection automatically handles class dependencies through service containers in Laravel without manual new objects. Its core is constructor injection and method injection, such as automatically passing in the Request instance in the controller. Laravel parses dependencies through type prompts and recursively creates the required objects. The binding interface and implementation can be used by the service provider to use the bind method, or singleton to bind a singleton. When using it, you need to ensure type prompts, avoid constructor complications, use context bindings with caution, and understand automatic parsing rules. Mastering these can improve code flexibility and maintenance.

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.

Methods to manage database state in Laravel tests include using RefreshDatabase, selective seeding of data, careful use of transactions, and manual cleaning if necessary. 1. Use RefreshDatabasetrait to automatically migrate the database structure to ensure that each test is based on a clean database; 2. Use specific seeds to fill the necessary data and generate dynamic data in combination with the model factory; 3. Use DatabaseTransactionstrait to roll back the test changes, but pay attention to its limitations; 4. Manually truncate the table or reseed the database when it cannot be automatically cleaned. These methods are flexibly selected according to the type of test and environment to ensure the reliability and efficiency of the test.

LaravelSanctum is suitable for simple, lightweight API certifications such as SPA or mobile applications, while Passport is suitable for scenarios where full OAuth2 functionality is required. 1. Sanctum provides token-based authentication, suitable for first-party clients; 2. Passport supports complex processes such as authorization codes and client credentials, suitable for third-party developers to access; 3. Sanctum installation and configuration are simpler and maintenance costs are low; 4. Passport functions are comprehensive but configuration is complex, suitable for platforms that require fine permission control. When selecting, you should determine whether the OAuth2 feature is required based on the project requirements.

Laravel simplifies database transaction processing with built-in support. 1. Use the DB::transaction() method to automatically commit or rollback operations to ensure data integrity; 2. Support nested transactions and implement them through savepoints, but it is usually recommended to use a single transaction wrapper to avoid complexity; 3. Provide manual control methods such as beginTransaction(), commit() and rollBack(), suitable for scenarios that require more flexible processing; 4. Best practices include keeping transactions short, only using them when necessary, testing failures, and recording rollback information. Rationally choosing transaction management methods can help improve application reliability and performance.
