DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23542>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23542 [PATCH/BUG] Better handling of CLOB in esql (get-xml) and handling of Oracle 'temporary lobs' [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2003-10-07 08:39 ------- Still see that esql.xsl is not handling properly the clobs. The problem is that: get-xml calls get-string, which calls get-string-encoded, which calls getAscii. You right that getAscii handles clob, but it wrongly handles the character encoding of clob - for Oracle with UTF8, the stream is cut on first national character. In getAscii: asciiStream = new BufferedInputStream(dbClob.getAsciiStream()); In getStringOrClob: reader = new BufferedReader(dbClob.getCharacterStream()); In case of getStringOrClob, UTF-8 stream is read properly. I haven't got knowledge of any other DB which supports CLOB and UTF-8, but in case of Oracle, the only correct reading from Clob is through dbClob.getCharacterStream(). So it is why I requested to handle somehow get-xml, that in case of CLOB , dbClob.getCharacterStream() is used instead of getCharacterStream()!!!. Probably it works correct for other DB - but not sure.
