Re: Pro*C 2.0 "char" bug

For Pro*C 2.0.x the following rule was enforced:

 If you have a single character field that you want to select into a Pro*C  host variable of type char, you either need to use the precompiler option  dbms=v6_char or change your host variable to char[2].

Ken Denny wrote:
>
> Rick Wiggins wrote:
> >
> > We've noticed an erroneous behavior with Pro*C 2.0 that doesn't seem
 to
> > be present in versions 1.6 or 2.2. In version 2.0, if a CHAR(1)
> > database column is SELECTed into a "plain old char" variable that's
> I experienced a similar problem when I went from 1.6 to 2.0. I was
> constructing a string in some PL/SQL code in a Pro*C program and
> trying

MSc. Bo Stern                         Office: Phone +45 44 80 84 12
Systems Engineer/Technical Analyst            Fax   +45 44 80 80 91
Oracle Denmark A/S                            Email bo_stern_at_iname.com
***************** http://home5.inet.tele.dk/bo_stern *****************
      The statements and opinions expressed here are my own and 
          do not necessarily represent those of my employer.