Charset issue about atom-build-oracle HOT 10 CLOSED

Do you get the same if you compile the file directly in SqlPlus/SQLcl, from command prompt?
Do you have NLS_LANG environment var set?

This post suggests you can query v$session_connect_info to find out what is being used.

Haven't tested yet, just a couple of thoughts in the meantime.

from atom-build-oracle.

It works well when compiling directly from SQLcl (command prompt).

I could not find anything useful with v$session_connect_info, but I ran the following in both Atom (SQLcl) and Command Prompt (SQLcl):

select * from v$nls_parameters
where parameter = 'NLS_CHARACTERSET'
;

and got the same result:

PARAMETER                                                        VALUE
---------------------------------------------------------------- ----------------------------------------------------------------
NLS_CHARACTERSET                                                 AL32UTF8

One character that fails is é, you can try with:

create or replace package nls_test
is
    dummy number; -- éééééé
end nls_test;
/

Furthermore, it works from Atom when using Windows 1252 instead of "UTF-8". Weird.

from atom-build-oracle.

When querying that view v$session_connect_info, I can see that SQL*Plus sets the client charset to US7ASCII, whereas SQLcl and SQL Dev has it as Unknown. I had a look at the statements window in SQL Dev to see if anything is set as far as encoding is concerned, but there doesn't appear to be.

On the command line, if I do: export NLS_LANG=.AL32UTF8 before connecting to SQL*Plus, the compilation succeeds (as in, accented character persists). Proposed solution is a new configuration item for NLS_LANG, with a default value of AL32UTF8. Set that variable only if there isn't a current environment variable for that.

from atom-build-oracle.

Thanks Trent. Now it works in SQL*Plus but still not in SQLcl.

from atom-build-oracle.

Oh yes, I tested SQLcl in my system and it worked. Just tested in Windows and see the issue still there.

from atom-build-oracle.

I pinged the team on Twitter, as I'm not quite sure how to resolve this.

Also found this thread https://community.oracle.com/thread/3923443?start=0&tstart=0, which suggests it should just work without setting anything.

from atom-build-oracle.

Do you think this is doable within atom-build-oracle?

from atom-build-oracle.

Yeah, I think it should be. Need to get in there and give it a better test, and think of the best way to add it in (through a config or just do it always by default). Will try get onto this next week (if not before).

from atom-build-oracle.

@vincentmorneau Did you want to give that a test? It seemed to be working, but thought better get a second test before closing.

from atom-build-oracle.

Works perfectly. This tool is great! Thanks Trent.

from atom-build-oracle.