Exercise 1: The Hybrid, a Fourth Independent Time — Possible Solution
====================================================================

THE HYBRID ITSELF
------------------------------
Per this chapter, the adjacency-list-plus-materialized-path hybrid stores both a real parent foreign key and a precomputed full path string on every row, so a page's ancestry can be walked structurally through parent_id when needed, while reading or looking up a page by its full URL path doesn't require walking the tree at all.

THE TWO PIECES OF INFORMATION ON EACH Page ROW
------------------------------
Per this chapter, each Page row stores parent_id (the adjacency-list half, a real foreign key referencing another row in the same pages table) and full_path (the materialized-path half, a precomputed string built from every ancestor's own slug plus this page's own slug).

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly describes what the hybrid provides - structural ancestry via the foreign key, fast path lookup via the precomputed string - and correctly names parent_id and full_path as the two specific columns responsible for each half.