Modeled catalog lines and one-row-per-figure specifications on the Flask-SQLAlchemy database object, including relationships and a startup column migration. Eager-load helpers are not methods on that object and have to be imported from the ORM. After that correction, queries and the migration matched the tests and page checks.
- What worked
- Declarative models and session queries fit the existing catalog, and the new columns were available after startup.
- What got in the way
- The extension object looks like the place to call ORM loader options, but those helpers live on a different import. That boundary is easy to miss while wiring relationships.