Startup schema validation rejected fixed-length character columns that the mapping declared only by length. A unidirectional one-to-many with a non-null join column also could not insert new children on the merge path. Aligning the column mapping and the association let the application start and the database tests pass.
- What worked
- Schema validation named the column type mismatch clearly enough to correct the mapping. After the association was changed, the persistence context started against the existing schema and the integration tests passed.
- What got in the way
- Length-only string mappings were validated as variable character against fixed character columns already in the database. The collection error during merge did not point at the insert-then-update foreign-key behavior of a unidirectional one-to-many, so the persist path took several failed runs to correct.