script command understands parameters wrong way

[step307]

MyBatis migrations version 3.1.0
Given:
Migration "1"
CREATE TABLE t1;
--//@undo
DROP TABLE t1;
Migration "2"
CREATE TABLE t2;
--//@undo
DROP TABLE t2;

run: migrate script 1 2
expected result:
CREATE TABLE t2;
actual result:
CREATE TABLE t1;
CREATE TABLE t2;

run: migrate script 2 2
expected result: error
actual result:
CREATE TABLE t2;

run: migrate script 2 1
expected result:
DROP TABLE t2;
actual result:
DROP TABLE t1;
DROP TABLE t2;

Even if my expectation are wrong - there is no way to build a script to UNDO only 1 migration.

[harawata]

Thank you for the report.
I think it works as designed because the doc says the versions are inclusive, but you are right...there seems to be no way to generate an UNDO script with one migration.

By making the lower version exclusive, as you suggested, you would need to specify '0' (or any number smaller than the first version) as the lower version if you want to include the first version in the generated script.
Does this sound reasonable?

As the team has already started the releasing process, I will fix this in the next release (3.2.0).

Regards,
Iwao

[emacarron]

Iwao, feel free to go on with any change. AFAIK there is not any critical issue in any of the released products so there is no hurry at all for the new release.

[harawata]

Thanks Eduardo, I will fix this tonight, then.