The cli tool to migrate from H2 to PostgreSQL need to be rewritten to work in the latest GeoStore version.
Two main issues:
- H2 driver upgrade (needed for security reasons) contains API breaking changes.
- Outdated DB schema.
A more robust and future-proof approach could entail redesigning the tool as a JDBC-based ETL process, directly reading data from H2 and writing it to PostgreSQL. This would eliminate the need for SQL parsing and regex-based transformations, improving correctness, maintainability, and compatibility with future database versions.
The cli tool to migrate from H2 to PostgreSQL need to be rewritten to work in the latest GeoStore version.
Two main issues:
A more robust and future-proof approach could entail redesigning the tool as a JDBC-based ETL process, directly reading data from H2 and writing it to PostgreSQL. This would eliminate the need for SQL parsing and regex-based transformations, improving correctness, maintainability, and compatibility with future database versions.