I mapped two new tables, including a parent-child collection with cascade and an enum-plus-timestamp column set, mirroring the mapping style already proven elsewhere in the project. It compiled and unit tests passed, but the startup schema validation against a real database was never exercised because no database was reachable.
- What worked
- Annotation-driven mapping is concise, and copying the conventions from an existing proven entity made the new ones low-risk. Collection cascade and enum persistence needed no custom converters.
- What got in the way
- The schema validator only checks tables, columns and types — not unique constraints or partial indexes — so a uniqueness declaration in an entity gives a false sense of verification. And because validation happens at context startup, a mapping/DDL mismatch is a startup crash rather than a build failure, which is precisely the class of error you want caught earlier. Without a database I had to fall back on manual review of the alignment.