You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Hi, I’m interested in contributing to this issue. I noticed that it is currently open and there is no assignee or linked pull request.
I would like to work on implementing the schema version information inside the database and investigate the existing migration/versioning approach before making any changes.
Would it be okay for me to take up this issue and submit a pull request?
Activity
subhechhamaiti716-byte commentedon Sep 23, 2026
Hi, I’m interested in contributing to this issue. I noticed that it is currently open and there is no assignee or linked pull request.
I would like to work on implementing the schema version information inside the database and investigate the existing migration/versioning approach before making any changes.
Would it be okay for me to take up this issue and submit a pull request?