Exercise 2: Why meals Is a String, Not Json — Possible Solution
====================================================================

WHAT THE CHAPTER FOUND
------------------------------
Prisma does offer a dedicated Json field type in schema.prisma. Checked
directly against Prisma's own real, current issue history rather than
assumed, its support for that type on the SQLite provider specifically
has been genuinely inconsistent across versions - open bug reports
exist even in cases where partial support has been added, and older
discussions describe it as unsupported outright for a long stretch of
Prisma's own history.

WHY THAT LED TO STORING meals AS A PLAIN STRING
------------------------------
Rather than build this course's own recipe caching around a feature
whose current, exact level of SQLite support isn't fully settled or
verifiable with confidence, RecipeCache stores the meal list the same
way the sibling course's raw SQL table does - as a plain text column,
serialized to a JSON string with JSON.stringify() before writing and
parsed back with JSON.parse() after reading. This sacrifices a small
amount of Prisma-side convenience (no built-in JSON querying) in
exchange for behavior that doesn't depend on a still-uneven feature.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly cites the specific, checked reason (SQLite's own JSON
field support being inconsistent, not simply "Prisma doesn't do JSON"
in general - it works better on other providers), and it correctly
explains the actual design tradeoff being made rather than treating the
plain-String choice as an arbitrary stylistic decision.