Skip to content

Conversation

@hopkink1
Copy link

Upgrade Mybatis-Migration support to 3.3.7 to work around an error introduced by mybatis/migrations@a5d8a72#diff-2c0b0afa4090a13167224923f2536046. Also by checking if the script file exists before creating a MigrationReader, code now handles case when onabort.sql isn't found.

…troduced by mybatis/migrations@a5d8a72#diff-2c0b0afa4090a13167224923f2536046. Also by checking if the script file exists before creating a MigrationReader, code now handles case when onabort.sql isn't found.
@hopkink1
Copy link
Author

hopkink1 commented Jun 8, 2020

@Bessonov Any thoughts on this PR?

I see that the CI checks failed, but it doesn't look to have anything to do with the changes here.

@Bessonov
Copy link
Owner

Bessonov commented Jun 8, 2020

@hopkink1 @bliessens thank you for your contributions! I'm not using it anymore, because I've switched from Java to TypeScript and therefore I can't test it or support you. Would you like to move it to a new org? I've noticed that there is an official integration: https://github.com/mybatis/spring-boot-starter It should be better than my integration. What do you think?

@hopkink1
Copy link
Author

I believe mybatis/spring-boot-starter helps with using mybatis in the application, but doesn't specifically deal with mybatis-migrations, which is where your project fit in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants