Exercise 3: Confirming Automatic utf8mb4 in Prisma's Own Migration — Possible Solution
====================================================================

RUNNING THE MIGRATION
------------------------------
Per this chapter, a fresh npx prisma migrate dev generates a new SQL
migration file under prisma/migrations/, without any manual charset or
collation setting having been added anywhere in schema.prisma or the
database connection URL.

INSPECTING THE GENERATED SQL
------------------------------
Opening that migration file's own migration.sql shows the CREATE TABLE
statement for the Page table ending with a clause reading something
like:

) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

CONFIRMING NOTHING MANUAL WAS ADDED
------------------------------
Reviewing schema.prisma (from Chapter 2) and lib/prisma.ts (from
Chapter 2's Client Extension) confirms neither file contains any
charset- or collation-related configuration - the model definition is
just field types and relations, and the Prisma Client setup is just the
extension logic from Chapter 2. The utf8mb4 clause in the migration SQL
was generated entirely by Prisma's own default behavior.

WHY THIS WORKS AS AN ANSWER
------------------------------
It locates the actual generated SQL rather than trusting the claim, and
separately confirms the absence of any manual configuration that could
have produced the same result some other way - directly verifying this
chapter's own "automatic, no configuration needed" claim, and the
contrast it draws against Astro Rebuild's own Drizzle setup, which
needed an explicit charset: 'utf8mb4' line to reach the identical
outcome.