[BUG] - Database validation error with liquibase

[kors2m]

Jimmer Version

0.9.77

JDK Version

21

Database

Postgres

OS

Linux

Expected behavior

Database validation after liquibase migrations

Actual behavior

Database validation occurs before liquibase migrations

Description

After updating Jimmer from 0.9.74 to 0.9.77, have a problem with liquibase migrations.

Reproduction steps

https://github.com/kors2m/jimmer-issue

Generated SQL

No response

Relation Model

No response

Screenshots

No response

Logs

jimmer.log

[babyfish-ct]

The behavior changed is required by another user uses liquibase.

Now, if database if createed by liquibase, please use manual validation API to control the validation time by your self

• Keep the database validation to be NONE(validation will not be validated automatically)
• Call sqlClient.validateDatabase() to validate database manually when you think your liquibase intialization is one

[kors2m]

I think most projects have a fairly simple process of initializing the database via liquibase/flyway, and it turns out that automatic validation does not support this anymore.
And you need to add a separate configuration for validating the database to the application and to integration tests.

I would like it to be out of the box or through the Jimmer settings.

[babyfish-ct]

Previously, Jimmer solved this problem by lazily initializing SqlClient in Spring. However, users who adopted the multi-data source mode reported that this mode caused problems in their reference scenarios.

There are too many user scenarios, and now I can't quicly find a way to have the best of both worlds. It may take some more time. However, at least there is a work around now, and you can continue your work.