You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the Java engine derives the encoding for the console from the shell it is currently running on. In that case of the Slovenian machine it seems that it is not possible to deal with that codepage.
There is a workaround by setting the encoding explicitly at runtime:
-Dsun.stdout.encoding=Cp1250
Perhaps there is another explanation / workaround.
This will not have any negative impact because it only sets the character set for the console output. It does not affect the sql scripts that are executed nor the generated logfiles.
When running on a Slovenian environment, we get a warning regarding the encoding cp1250.
The text was updated successfully, but these errors were encountered: