Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Pro*C Character set problems

Re: Pro*C Character set problems

From: John Tower <jtowerjr_at_towergroupinc.com>
Date: Fri, 31 Aug 2001 13:07:59 GMT
Message-ID: <Xns910E5D4EE2CF9jtowerjr@64.154.60.173>


pbsis_at_hotmail.com (Richard Lister) wrote in news:4e0a7502.0108310457.4160f279_at_posting.google.com:

> We are modifying a system that uses Oracle Pro*C to read large text
> strings from Oracle 8 CLOB columns.
>
> The system currently only stores ASCII characters (codes 0 - 127).
>
> We have a required to store extended characters (128-255).
>

- snip -  

> It would appear that despite the database's character set
> configuration, our Pro*C program is only configured to support the
> basic ASCII character set and when we retrieve data from the CLOB, any
> extended characters are converted to an appropriate ASCII value. The
> 163 is a £ sign that would explain why it is converted to # unlike the
> two unknown characters that are converted to '?'.
>

- snip -

            Have you tried using unsigned char instead of char as the host     variable datatype? Char has a range of -128 to 127 while unsigned     char has range of 0 - 255.

John Received on Fri Aug 31 2001 - 08:07:59 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US