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
Validate migration encoding #2069
Command Line Client
MSSQL 2012 Enterprise
What did you do?
I work with SQL developers who, somehow, manage to create and add a multitude of variously encoded .sql files. For many these do "Fail Fast" but in particular ANSI-encoded files will still execute... with botched characters. This is particularly dangerous.
What do you want to see?
I have loved flyway so far and hope this doesn't come across as entitled. I think an encoding check for the migrations folder would be a great idea especially for these corner cases that can seriously ruin a whole migration. For teams that have automated fully and can't manage to enforce encoding, this will help avoid problems.
Right now my workaround will be to write a powershell script that performs this as part of our Pull Request, Gated Commit process.
changed the title
Fail Migration (or make configurable?) when a migration file violates encoding parameter
Jul 6, 2018
We have now addressed this at least partially. Flyway will now complain when it is configured for