Exercise 2: The Field-Naming Difference — Possible Solution
====================================================================

THE DIFFERENCE
------------------------------
The sibling course's raw SQL schema uses snake_case column names —
expiry_date, added_at, used_at — matching common SQL naming convention.
This course's Prisma schema uses camelCase field names instead —
expiryDate, addedAt, usedAt — matching Prisma's own idiomatic
JavaScript/TypeScript-facing convention.

WHAT THIS ACTUALLY AFFECTS
------------------------------
Every JSON response this course's API sends back uses the camelCase
names, since Prisma Client returns objects shaped exactly like the
schema's own field names. The sibling course's API returns
snake_case-named fields instead. This means the React frontend for this
course has to read item.expiryDate, while the sibling course's frontend
has to read item.expiry_date — the two frontends are not
interchangeable without translating field names, even though they're
displaying the exact same underlying data for the exact same app.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies the naming convention difference itself and,
more importantly, names a concrete, practical consequence (the shape of
the JSON payload the React frontend actually consumes) rather than
treating the naming difference as purely stylistic with no real effect
on the rest of the app.