Exercise 2: "A Database Is a File" and Why File-Copy Backups Work — Possible Solution
====================================================================

WHAT "A DATABASE IS A FILE" MEANS CONCRETELY
------------------------------
Per this chapter, "the entire database — schema, tables, indexes, all
data — lives in a single ordinary file on disk... opening a database
is as simple as opening that file." Every piece of a SQLite database
— its table definitions, its index structures, and every row of
actual data — is stored inside one single, ordinary file that any
operating system already knows how to work with (copy, move, rename,
inspect the size of) without needing any database-specific tooling to
do those basic file operations.

WHY cp mydata.db backup.db CAN BE A COMPLETE, VALID BACKUP
------------------------------
Per this chapter, "that single command is a complete, valid backup"
(with the noted caveat about no write being in progress). Because
EVERYTHING that makes up the database — not just the data, but the
schema and indexes too — lives inside that one file, copying the file
at the operating-system level genuinely captures the entire database
in one operation. There's no separate metadata living elsewhere, no
server-side state to also capture, nothing else that needs to be
gathered up alongside the file to have a complete, restorable copy of
the database.

WHY MYSQL/POSTGRES HAVE NO DIRECT EQUIVALENT
------------------------------
Per this chapter, "in MySQL or Postgres, a 'database' is a logical
construct managed by a running server process, spread across the
server's own internal storage structures... copying or backing up a
database means using the server's own dump/export tooling." A MySQL
or Postgres database isn't a single, self-contained file a user could
simply copy — it's data managed and organized internally by the
running server process, potentially spread across multiple internal
files/structures the server itself controls, and generally not safe
or even meaningful to copy directly at the filesystem level while the
server is running. Getting a real backup requires going through the
server's own dump/export mechanism (like mysqldump or pg_dump),
producing a separate export file — a fundamentally different, more
involved process than SQLite's own direct file copy.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains precisely what "the database is the file" means in terms
of what the file actually contains, and contrasts that directly with
why MySQL/Postgres require a dedicated export tool rather than a
simple file copy, using the chapter's own explanation of why their
data isn't self-contained in a single copyable file the same way.