Dear Gustaf (and all)
thanks Gustaf for the fixes - reading your code, it's interesting to see how
AOLserver works internally. And it's all so elegant, meaning even I can follow
it! I can confirm your fix has resolved the 413 problem. I attempted to take it
a step further and add a 413
I am having trouble getting Chinese characters in/out of oracle with
AOLserver. Here is my stack:
Oracle 11g
TCL 8.5
AOLserver 4.51
Oracle Driver version 2.7
The existing database has a database character set of WE8ISO8859P1.
But we are using NCHAR and NVARCHAR2 datatypes to store Unicode
Just a quick shot in the dark here.
I have ran into encoding issues in the past because by default TCL will assume
everything is Latin-1 and it is not always straight forward when a conflict
will happen.
You can set a variable like $first_names to be a UTF-8 string and it can be
written
I've had to deal with Chinese Characters and Postgres. I don't recall all the
details anymore but I do recall what Peter is saying, that Tcl was a culprit
more than the database.
I would use sqlplus to check what myform.tcl is inserting into the database.
That will at least tell you whether
