New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spring-boot stops when driver could not establish the connection #775
Comments
With the property javers.sqlSchemaManagementEnabled set to false, method JaversSchemaManager.ensureSchema is not called and so the schema is not updated. public void ensureSchema() {
if (javersSqlRepository.getConfiguration().isSchemaManagementEnabled()) {
TransactionTemplate tmpl = new TransactionTemplate(txManager);
tmpl.execute(new TransactionCallbackWithoutResult() {
@Override
protected void doInTransactionWithoutResult(TransactionStatus status) {
javersSqlRepository.ensureSchema();
}
});
}
} But I'm not sure it's the cleanest way to introduce this behaviour. @bartoszwalacik, what do you think? |
Or maybe we should think of a different way of triggering JaversTransactionalDecorator.ensureSchema than PostConstruct annotation. I assume it was used to ensure schema update before actual data processing. |
@mwesolowski your solution would be good enough. I don't have a better idea. |
Please, could it be added for the next version? We're having problems with it. |
If you want it to be fixed, consider to contribute. |
#775 Solving issue when can't establish connection
fixed in 5.6.0 |
Application fails when driver could not establish the connection. Is there any possibility to disable ensureSchema method when javers.sqlSchemaManagementEnabled=false?
I am using spring-boot 2.0.1.RELEASE with:
application.properties:
javers.sqlSchemaManagementEnabled=false
Stacktrace:
The text was updated successfully, but these errors were encountered: