Flyway does not reset the current schema between migrations #1108
If a migration includes a statement like:
... the current schema of the database connection is not reset by flyway before subsequent migrations are executed, potentially leading to unintended consequences, such as creating tables in the wrong schema.
See the end of this description for example migrations.
Note that the end result of these two sets of commands would produce different results:
This issue was initially found on an Oracle 11g database, using flyway versions 3.0 and 3.2.1.
The text was updated successfully, but these errors were encountered: