Schema Migrations - Statement commit not working as expected about mybatis HOT 6 CLOSED

Fixed.

[deleted comment]

Thanks for the fix

I've created unit tests (attached) that you might want to add.

As you'll see BaseMigratorTest & MigratorTransactionTest go into
org.apache.ibatis.migration package, while the transaction.zip is the package 
that
contains the configuration - it also goes into org.apache.ibatis.migration

I initially tried to just add the test to the current MigratorTest class, but 
it just
caused problems with it's own tests due to the nature of the new scripts. So, I 
opted
for a config with separate script files.

The tests cover both autocommit true & false, while also testing positive and
negative scenario's. I also created BaseMigratorTest, it just contains 
functionality
currently found in MigratorTest, which I wanted to re-use. I did not modify
MigratorTest, wanted to see if you like the base class first, maybe you have 
some
other ideas...

Hi guys, 

The issue is available in the version 3.2.0. 

Having autocommit=false and two sql statements in the script - first statement 
is being committed in spite of the error thrown by the second statement. 

Can you please check and confirm that the bug isn't back? 

Regards,
Edgar