Exercise 1: This Course's Core Comparison Claim — Possible Solution
====================================================================

THE CORE CLAIM, IN ONE SENTENCE
------------------------------
This course rebuilds the exact same app as Food Tracker (React + Express),
in the exact same React + Express architecture, changing only how the
server talks to the database — Prisma's generated, schema-derived query
methods in place of the sibling course's hand-written SQL via
better-sqlite3.

THE ONE CONCRETE RISK PRISMA INTRODUCES THAT RAW SQL DOESN'T HAVE
------------------------------
Prisma Client hides the actual SQL being executed behind its generated
methods. That's genuinely convenient day to day, but it also makes it
easy to introduce an N+1 query problem without noticing — a loop that
reads like ordinary JavaScript can quietly issue one database round-trip
per iteration instead of a single query, and nothing in the code itself
flags it the way a raw SQL query sitting right there in the route handler
would.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies that the app and the architecture are unchanged —
only the data-access layer differs — and it names a real, specific cost
of that change (the N+1 risk hidden behind Prisma's abstraction) rather
than treating Prisma as free convenience with no downside, matching the
chapter's own honest framing.