The encoding of SQL migrations.
The encodings that Flyway supports are:
US-ASCII
ISO-8859-1
UTF-8
UTF-16BE
UTF-16LE
UTF-16
We recommend using a consistent file encoding across all of your scripts to minimize the issues you encounter. See Troubleshooting for known problems and solutions.
UTF-8
./flyway -encoding="UTF-16" info
flyway.encoding=UTF-16
FLYWAY_ENCODING=UTF-16
Flyway.configure()
.encoding("UTF-16")
.load()
flyway {
encoding = 'UTF-16'
}
<configuration>
<encoding>UTF-16</encoding>
</configuration>
This is because some encoding names are synonyms for others. For instance, an editor which specifies ANSI
is actually ISO-8859-1
.
This exception is due to inconsistent encoding configurations. ISO-8859-1
is the most compatible supported encoding, so using this encoding could fix your configuration. However, we recommend that all of your scripts have the same encoding.