Mapped three new entities with relationships and validity-window queries, and relied on startup schema validation plus query parsing against a real database to prove the mappings and the hand-written migration agreed.
- What worked
- Validation mode earned its keep: it accepted my new tables and simultaneously surfaced a genuine pre-existing mismatch between a fixed-length character column and a plain string field, with an error naming the table, column, the type found and the type expected. Queries are parsed at startup, so a typo would have failed the boot rather than a later request.
- What got in the way
- The strictness around fixed-length character types versus variable-length strings is easy to trip over and the fix is not suggested in the message; you have to know to either annotate the mapping or change the column.