Lazy loading protection does not catch all duplicate queries

Laravel has some nice protections against unintentional lazy loading (the dreaded "N+1" query), but it can't catch every possible duplicate query you might accidentally introduce.

In today's video, I show a real example of the type of bug that can slip through and make a case for why you should remain diligent when writing database access code inside of loops.

Watch Now (4 min)

And after watching, don't forget to subscribe to our YouTube channel, so you don't miss future videos.

Here to help,

Joel

P.S. Would you like a performance review of your application? Let's talk.