btlqql opened a new pull request, #1377:
URL: https://github.com/apache/rocketmq-dashboard/pull/1377

   ## Summary
   
   - add an opt-in `postgresql` Spring profile while keeping the existing 
MySQL/H2 defaults unchanged
   - add the PostgreSQL JDBC driver and Flyway PostgreSQL support
   - provide a versioned PostgreSQL baseline covering all 15 Studio-owned 
persistence tables and indexes
   - configure MyBatis Plus for the PostgreSQL database id and automatic schema 
migration
   - document the PostgreSQL deployment environment variables
   - add Testcontainers coverage that boots the Spring context and exercises 
MyBatis CRUD against PostgreSQL 16
   
   ## Why
   
   Issue #956 asks for PostgreSQL persistence support. The current datasource 
configuration and schema are MySQL-oriented, so pointing Studio at PostgreSQL 
is not enough: startup schema initialization, data types, identity columns, 
booleans, and index naming all need a PostgreSQL-compatible path.
   
   This change makes PostgreSQL explicit and opt-in. It does not change the 
default development or production datasource behavior.
   
   ## Validation
   
   - `mvn -DskipTests=false -Dtest=PostgresqlPersistenceIntegrationTest test` 
(compilation and Checkstyle pass; Testcontainers is skipped locally because 
Testcontainers 1.21.2 cannot negotiate with Docker Desktop 29)
   - `mvn -DskipTests=false -Dtest=StudioApplicationTest test`
   - PostgreSQL 16 + Flyway 11.7.2 manual migration: all 15 Studio tables 
created, history version recorded, second migration is a no-op
   - started the actual application with `SPRING_PROFILES_ACTIVE=postgresql`; 
`/actuator/health` returned `UP`
   - verified instance create/list/delete through `/api/instances` against 
PostgreSQL and confirmed the final database row count returned to zero
   
   Fixes #956
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to