Laravel has some nice protections against N+1 queries, but they're only designed to catch certain patterns. In today's video, I walk through an example that slipped past those protections to show the importance of remaining alert.

masteringlaravel.io/daily/2025-09-19-video-lazy-loading-protection-does-not-catch-all-duplicate-queries

Lazy loading protection does not catch all duplicate queries | Mastering Laravel

From: masteringlaravel.io

Did you know you can render a Blade template inline? This isn't a feature I reach for frequently, but it's good to know it exists. Here is one use case where we found it quite handy.

masteringlaravel.io/daily/2023-09-06-when-might-you-render-a-blade-template-inline

When might you render a Blade template inline? | Mastering Laravel

From: masteringlaravel.io

Finishing up my discussion on Postgres route model binding quirks, here are two other possible fixes that I think have some advantages over the approach I shared previously.

masteringlaravel.io/daily/2025-09-17-two-other-ways-to-fix-postgres-route-model-binding-behavior

Two other ways to fix Postgres route model binding behavior | Mastering Laravel

From: masteringlaravel.io

Keeping the discussion going from yesterday's tip about Postgres route model binding differences, here's one approach to fix it and analysis of whether or not we should even bother.

masteringlaravel.io/daily/2025-09-16-one-approach-to-handling-postgres-route-model-binding-issues

One approach to handling Postgres route model binding issues | Mastering Laravel

From: masteringlaravel.io

Even with a full-featured ORM like Eloquent, databases aren't quite as easy to interchange as we might hope. Here's an example of how route model binding works differently between MySQL and Postgres.

masteringlaravel.io/daily/2025-09-15-route-model-binding-works-differently-between-mysql-and-postgres

Route model binding works differently between MySQL and Postgres | Mastering Laravel

From: masteringlaravel.io