Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
UTF-8 BOM stripping no longer works in 6.0.0-beta2 #2413
Which version and edition of Flyway are you using?
Flyway Community Edition 6.0.0-beta2 by Boxfuse
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Issue occurs on 6.0.0-beta2. Does not occur in Flyway 5.2.4
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Which database are you using (type & version)?
Microsoft SQL Server 2017 Developer Edition
Which operating system are you using?
Windows 10, 1903
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
Create a simple migration with valid SQL Server syntax. Save the migration in "UTF-8 with BOM" encoding. Run "flyway migrate"
What did you expect to see?
Migrations succesfully applied.
What did you see instead?
On a clean database, applying the migrations via Flyway 6.0.0-beta2, I get:
On an existing database that has been previously migrated with Flyway 5.2.4, I get the following, even though the migration scripts themselves have not changed:
It looks like the BOM stripping is not working properly in 6.0.0-beta2