I don't think it's tcl at this point. I can see that aolserver/tcl can bring
in the unicode characters and return them to the client 'as is'.
And you can see what encoding system tcl is using via this command as well:
[encoding system]
which shows that tcl is using UTF-8, which is what is
It might be that the Oracle driver doesn't handle those column types. Is there
anything in the AOLserver log? Maybe turn on debug to get more info.
Brian
From: AOLserver Discussion [AOLSERVER@LISTSERV.AOL.COM] On Behalf Of Brad Chick
I just grabbed the latest oracle driver from cvs and you are right: there is
no explicit support for either NCHAR or NVARCHAR2 - which oracle requires to
store unicode characters.
So, I will try to update the driver and report back.
Thanks
--
AOLserver - http://www.aolserver.com/
To Remove
Well, I reached an impasse. I grabbed the latest source from CVS, added
support for the 2 datatypes (NCHAR, NVARCHAR2), and recompiled. Then, I
turned on debugging for the driver.
The logs look great. The driver constructs the queries appropriately:
e.g.
Make sure that any vars set in your shell environment that relate to this are
also set in your nsd wrapper script. I wish I knew for sure if that is enough
for them to be effective, but I don't. I vaguely recall that the C API the
driver uses is called Pro-C on the Oracle side - you might
