TOPIC
with() by default pulls every column from a related table — narrowing that down matters for a wide table, but forgetting the foreign key column produces a relationship that silently comes back null.
A cast is what turns a raw JSON text column into a working PHP array automatically on every read and write — without one, Eloquent hands back and expects a plain JSON string instead.
The four pieces of a real CRUD resource — listing with search and pagination, image-handled create/update, and safe delete — assembled into one practical, version-agnostic walkthrough.
Any operation touching more than one table — where a partial failure would leave the data in a genuinely inconsistent state — belongs inside a transaction, not left to run as separate, independent queries.
When a raw query is actually justified over Eloquent, and why parameter binding — not string concatenation — is the difference between a raw query and a SQL injection bug.
GROUP BY collapses rows into per-group summaries; HAVING filters those summaries afterward — the key distinction from WHERE, which filters individual rows before any grouping happens.
A second, separate database — legacy data, a read replica, a reporting warehouse — is configured as another named connection, and a model or query explicitly opts into using it.
whereIn, whereNull, orWhere, and a handful of siblings cover almost every filtering need — the one that actually causes bugs is orWhere's grouping behavior when mixed with other conditions.
A search or filter form where every field is optional usually ends up as a wall of if statements around a query — when() folds each one into a single fluent chain instead.
These three relationship types cover the majority of real-world table structures — the trick is remembering which side of the foreign key each one describes.
"Users who have at least one order over $100" can't be expressed with a normal where() clause — whereHas() is specifically for filtering a query based on a related model's data.
Five aggregate methods cover almost every "how many" or "what's the total" question — the one thing worth understanding is that each one executes its own query and returns a scalar, not a collection.
