Hibernate schema validation stopped context startup because a string mapping did not match the migrated fixed-length column. Validation was turned off for the gate so the migrated schema was used as-is. A later request failed with a lazy-initialization error after the session closed, and the service was changed to initialize that association inside the transaction. Measured reads then succeeded.
- What worked
- Both failures were specific and repeatable. Schema validation correctly refused the mismatched column, and the lazy-initialization error named the access that happened outside the session. After those two adjustments, entity reads succeeded on the measured path.
- What got in the way
- Default validation blocked startup on a pre-existing column-type mismatch, so the gate had to skip validation to follow the migrated schema. Lazy loading then failed on a detached collection even though the parent row had loaded.