Menene query builder kuma yadda ya danganta da Eloquent?

Question

Accepted Answer

Laravel's **Query Builder** shine fluent, chainable interface don gini da gudnatawa database queries ba tare da rubutu raw SQL ba. **Eloquent an gina shi akan jerin Query Builder** — Eloquent models suna amfani da shi a bãye, kuma Eloquent queries na iya amfani da duk Query Builder methods.

## Query Builder (database-level, ta hanyar DB facade)

```php
use Illuminate\Support\Facades\DB;

DB::table('users')
    ->where('active', true)
    ->where('age', '>', 18)
    ->orderBy('name')
    ->limit(10)
    ->get();                          // returns generic objects (not models)

DB::table('users')->where('id', 1)->update(['name' => 'X']);
DB::table('users')->insert(['name' => 'Ann']);
```

Query Builder yana aiki kai tsaye da tables (yana dawo da plain objects, ba Eloquent models ba). Yana da chain kuma **yana aiwatar parameter binding ta atomatik** — yana hana SQL injection.

## Eloquent yana amfani da fluent methods guda

```php
// Eloquent queries support ALL Query Builder methods (it's built on top)
User::where('active', true)
    ->where('age', '>', 18)
    ->orderBy('name')
    ->get();                          // returns User MODELS (with relationships, etc.)
```

Kuma ka yi chain methods akan Eloquent model, ka yi amfani da Query Builder a bãye — amma ka sami **models** (tare da relationships, accessors, da methods) maimakon plain objects.

## Advanced queries (duka suna goyin waɗansu)

```php
DB::table('orders')
    ->join('users', 'orders.user_id', '=', 'users.id')   // joins
    ->select('orders.*', 'users.name')
    ->where('orders.total', '>', 100)
    ->groupBy('users.id')
    ->havingRaw('SUM(orders.total) > 1000')
    ->get();

User::where('role', 'admin')
    ->orWhere('role', 'editor')
    ->whereIn('status', ['active', 'pending'])
    ->get();
```

Duka suna goyin joins, aggregates, subqueries, da complex conditions.

## Lokacin da za a yi amfani da wanne

```text
Eloquent (Model::...) → the default — get models with relationships/accessors/methods.
                        Best for most application logic.
Query Builder (DB::table) → when you want lightweight queries without model overhead,
                            complex reporting/aggregations, or to avoid loading models.
```

## Me yasa haka yake matukar muhimmi

Sanin Query Builder da dangantacewarsa da Eloquent yana da matukar muhimmanci don aiki kyau da databases a Laravel da zaɓi kayan dace ga kowane yanayi.

Maiya muhimmi ce cewa **Eloquent an gina shi akan jerin Query Builder** — don haka fluent, chainable methods da ka aiwatar akan Eloquent models (`where`, `orderBy`, `join`, da sauransu) sune Query Builder's, wanda nufin koyi gida ya koya muku dukansu.

Query Builder yana ba da hanya mai sauki, SQL-injection-safe (ta hanyar atomatik parameter binding) don gini queries ba tare da rubutu raw SQL ba, kuma Eloquent yana ƙara aiki model (relationships, accessors, methods) a jeri.

Sanin **lokacin da za a yi amfani da wanne** shine aiki ma'amalci: **Eloquent** don mafi yawan application logic (ka sami model objects masu arziki tare da relationships da halaye), da **Query Builder kai tsaye** (`DB::table`) don queries masu sauki ba tare da model overhead ba, complex reporting/aggregations, ko lokacin da ba ka buƙacin full models ba — wanda zai iya zama mafi aiki a wasu lokuta.

Duka suna jiyya complex queries (joins, aggregates, subqueries) tare da fluent API guda.

Sanin Query Builder, yadda Eloquent ya gina akan shi, shared safe parameter binding (hana SQL injection), da zaɓi tsakaninsu yana da matukar muhimmanci don rubutu aiki masu inganci, secure database code a Laravel, saboda database access yana tsakiya wuri a mafi yawan aikuki kuma zaɓin matakin dace (model-rich Eloquent vs lightweight Query Builder) yana tasiri clarity da performance.