The migration script encoding options within Flyway are defined by the Java character set.
In situations where a script’s encoding is either incorrect or cannot be reliably detected*, the product will continue processing without raising an explicit error. A debug‑level message is written if debug mode is enabled, and the system automatically falls back to UTF‑8. Depending on how similar your script’s actual encoding is to UTF‑8, the script may still run without obvious failures.
If you suspect this may be happening, please enable the debug switch so you can confirm whether encoding detection is failing.
*This assumes the following parameter is being used.
flyway.detectEncoding=true
2
-2
Was this article helpful?
0 out of 2 found this helpful
Articles in this section
- Where are Flyway CLI OSS artifacts
- Flyway has been compiled by a more recent version of the Java Runtime
- WARNING: An expired Flyway license key was provided; fell back to Community Edition.
- Azure DevOps self-hosted Flyway pipeline worked example SQL Server
- FlywayException: Invalid flag
- Flyway encoding support