As we have quite a few different Database Versions (and even more compatible Applications) it gets difficult to track which Database Version is actually deployed. As some applications may support multiple different schemas, deducing the schema version from the Application Version is very difficult.
It would be really helpful to have Version information (commit hash, release tag) somewhere inside the Database Schema itself. Ideally auto-updating via a maven plugin on each build.
Concrete Use Case:
- For migration scripts this would be very convenient to check whether the script can actually handle the specific versions and not just blindly try the migration.
As we have quite a few different Database Versions (and even more compatible Applications) it gets difficult to track which Database Version is actually deployed. As some applications may support multiple different schemas, deducing the schema version from the Application Version is very difficult.
It would be really helpful to have Version information (commit hash, release tag) somewhere inside the Database Schema itself. Ideally auto-updating via a maven plugin on each build.
Concrete Use Case: