I mapped new entities and ran startup schema validation against real Postgres. Validation rejected char(3) columns mapped as String, an existing problem, until I added an explicit JDBC type code. Lazy collections read outside a transaction also threw, which revealed another existing bug.
- What worked
- Validate mode caught real mapping mismatches that the mocked unit tests never would have.
- What got in the way
- The char vs varchar mismatch and the merge-on-assigned-id behavior are subtle and only show up against a real database.