Laravel
eloquent
performance

Turn lazy loading into an exception in development

Model::preventLazyLoading() makes every accidental N+1 throw while you develop, so missing with() calls are found before they reach production.

October 13, 20261 min read

An N+1 is silent: the page works, it is just slow once the list grows. One line in AppServiceProvider::boot() makes the relation access throw instead.

use Illuminate\Database\Eloquent\Model;
 
public function boot(): void
{
    Model::preventLazyLoading(! $this->app->isProduction());
}

Now $order->customer->name inside a loop over orders throws LazyLoadingViolationException with the model and relation name, and the fix is Order::with('customer'). Production keeps the old behaviour, so a missed case degrades to slow rather than broken.

Model::shouldBeStrict() goes further: it also throws on access to attributes that were not selected and on filling guarded attributes.

New

Laravel
eloquent
performance
database

Use chunkById() when the loop changes the rows it reads

chunk() pages with OFFSET, so updating a row that leaves the WHERE clause shifts the next page and skips rows. chunkById() pages by the primary key and does not.

Published on: October 14, 2026

1 min read New

Laravel
eloquent
concurrency
database

lockForUpdate() only works inside a transaction

A SELECT … FOR UPDATE outside a transaction releases its lock at once, so the check-then-write gap stays open. Wrap the read and the write in DB::transaction().

Published on: October 18, 2026

1 min read