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
I use your starter in our project and found an issue with the autoconfiguration order. Sometimes SqlSessionFactory and SqlSessionTemplate can be configured and used before liquibase/flyway initialized the database completely. That leads to
problems on startup in an empty environment.
As I checked, Liquibase/Flyway AutoConfiguration provides *DependsOnPostProcessors for standard JDBC beans (JdbcTemplate and EntityManager). That ensures the order in which beans will be initialized.
Now I added this dependency manually, but it will be nice if this will be in autoconfiguration.
Thank you in advance.
The text was updated successfully, but these errors were encountered:
We will consider to support the DependsOnPostProcessors on mybatis auto-configuration feature.
If possible, Could you provide a small reproduce project that occurred a problem and project that applied a workaround? We want to use it for testing.
@uladzislau-belykh
We resolved this issue on 2.3.0(not release yet, but you can use the snapshot version). 2.3.0 require to use together with Spring Boot 2.5+.
Hello,
I use your starter in our project and found an issue with the autoconfiguration order. Sometimes SqlSessionFactory and SqlSessionTemplate can be configured and used before liquibase/flyway initialized the database completely. That leads to
problems on startup in an empty environment.
As I checked, Liquibase/Flyway AutoConfiguration provides *DependsOnPostProcessors for standard JDBC beans (JdbcTemplate and EntityManager). That ensures the order in which beans will be initialized.
Now I added this dependency manually, but it will be nice if this will be in autoconfiguration.
Thank you in advance.
The text was updated successfully, but these errors were encountered: