Relied on the existing Flyway migrations to build the gate database schema during application startup. The migrated schema, including its fixed-length string column, was what the latency queries ran against after object-relational validation was skipped. No migration failure appeared on the runs that reached seeding.
- What worked
- Migrations produced a usable schema as part of context startup, without a separate migration command in the performance profile. The gate could follow that schema for the measured queries.