File checksum validation doesn't happen about r2dbc-migrate HOT 2 OPEN

2. has been done in 1.3.0

from r2dbc-migrate.

Seems like the library has the following logic : For a file named like V1__xxxxxx.sql , during migration, it parses the version , which is 1 here and checks in migrations table whether the record with id=1 is present. If it's there, it does nothing, else executes the script.

Thus even if we rename the file after __ (double underscore) keeping the version same, or change it's content, it simply ignores.

yes.

I think actually there are two issues:

1. calculate and validate checksums in order to prevent modifying already applied migrations
2. support schemas

1. looks complex to implement. I know Liquibase and Flyway have this, but is it common practice - to occasionally change already applied migrations ? I believe that the code review prevents this. In addition, in case when we have applied migrations V1 and V3, Liquibase allows to insert V2 between them. Anyway, PRs are welcome.
2. to solve this - I think to make migrator's schema and table names configurable.

from r2dbc-migrate.