×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have a couple of issues with viewing this data and wondered if anyone has
any advice:
With the CLOB being UTF-8, I haven't figured out an easy way to view the
data. Running SQL from ACS shows me data but it appears not to be handling
it correctly - the other character columns are CCSID 285 and appear ok but
the CLOB appears as gobbledegook.
I built the original data into the IFS as an xml document, and was able to
verify the content by viewing it in a browser which rendered the Japanese
and Greek characters properly.
I then read the data from the IFS file and wrote it to the CLOB in one
program, and ran another program to read it from the CLOB back to another
IFS file, which I was able to verify looked ok again in the browser. In the
absence of being able to view the data in the CLOB directly, I figured if I
could write it to the CLOB then read it back out ok, there was a fighting
chance the data in the CLOB was correct.
Anyway, ACS doesn't seem to translate the data in the CLOB correctly,
nether does squirrel-sql.
Good old green on black strsql doesn't make any attempt to access the data
( just shows it as *POINTER ). On another project when storing xml
documents in an xml data type, which was UTF-8, I could at least use the
xmlserialize function if I really had to access the data that way, but
there doesn't seem to be any equivalent for the CLOB.
Has anyone had any success at using ACS or squirrel sql to access UTF-8
data in a CLOB?
Thanks and regards,
Craig
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.