-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encoding error when importing the selected object #48
Comments
Have you tried also setting chcp in the intermediate sql.bat file (cliExecutable) setting? |
I also get the same error (????) and I use the following file.bat
the file.bat solves the problems of special characters when saving objects in the DB, but not when getting information from the DB. |
It probably depends on how the task to launch the command is configured. |
The oradew task which subsequently runs
I believe that is the reason why shellArgs don't do the trick here and I am not sure if it is possible to pass chcp to terminal used in processExecution and how.
Maybe changing the default code page of the terminal could help: |
Importing with "import selected object" is a different story as it save file on disk (not related to chcp). It should work with correctly setting property ( |
I do not recommend you to change the code page of the machine, it may stop the Windows operating system. |
@mickeypearce this is my oradewrc.json:
putting "source.encoding": "win1252" the problem is solved. my mistake |
When I import a DB package, using the "import selected object" function, the encoding is not respected. You can test using the WE8MSWIN1252 encoding
The text was updated successfully, but these errors were encountered: